[Bug 1495983] Re: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32
Tested the new wily kernel (32-bit kernel) on Hyper-V. The 4.2.0-17.21 kernel in testing boots fine. The 4.2.0-16.19 kernel crashes as reported above during boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495983 Title: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236455] Re: Running tasks are not subject to reloaded policies
Hi, this fixed it for me on saucy too, using linux- image-3.11.0-15-generic from -proposed. Before this kernel update, the virsh blockcopy would not work due to being blocked by apparmor. Regards, Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236455 Title: Running tasks are not subject to reloaded policies To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1236455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930962] Re: dhcp3-server reports many bad udp checksums to syslog using virtio NIC
Hi Dave, thanks for uploading that. I have upgraded the DHCP server system to Quantal: # dpkg -l | grep dhcp ii isc-dhcp-client 4.2.4-1ubuntu10.1amd64 ISC DHCP client ii isc-dhcp-common 4.2.4-1ubuntu10.1amd64 common files used by all the isc-dhcp* packages ii isc-dhcp-server 4.2.4-1ubuntu10.1amd64 ISC DHCP server for automatic IP address assignment I switched the NIC type to virtio and confirmed the problem still exists. I then installed the updated packages from quantal-proposed: # aptitude install isc-dhcp-server/quantal-proposed isc-dhcp-client /quantal-proposed isc-dhcp-common/quantal-proposed Confirming new versions: # dpkg -l | grep dhcp ii isc-dhcp-client 4.2.4-1ubuntu10.2amd64 ISC DHCP client ii isc-dhcp-common 4.2.4-1ubuntu10.2amd64 common files used by all the isc-dhcp* packages ii isc-dhcp-server 4.2.4-1ubuntu10.2amd64 ISC DHCP server for automatic IP address assignment The DHCP server log warnings do not appear any longer and DHCP is working as usual. So, it looks fixed to me. Thanks! Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930962 Title: dhcp3-server reports many bad udp checksums to syslog using virtio NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/930962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046340] [NEW] ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp
Public bug reported:
Hello,
in Lucid, Package: ntp (1:4.2.4p8+dfsg-1ubuntu2) has the file
/etc/logcheck/ignore.d.server/ntp included. This is used to configure
logcheck to ignore ntp messages in syslog that are not error conditions.
However:
In Natty, this file is not present in the ntp package
In Oneric, this file is not present in the ntp package
In Precise, this file is not present in the ntp package
When logcheck is installed, all ntp syslog messages are raised as alerts
by logcheck because the ntp configuration file is not present.
It would be helpful to have /etc/logcheck/ignore.d.server/ntp included
with ntp packaging as with Lucid.
Here are sample contents based on the Lucid version with the addition of
status change tot he time sync line.
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: time reset
[+-]*[0-9]{1,2}\.[0-9]{6} s$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronisation lost$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: no servers reachable$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronized to
([0-9.]{7,15}|[0-9a-fA-F:.]{4,39}), stratum [0-9]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronized to
LOCAL\([0-9]+\), stratum [0-9]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: kernel time sync
(disabled|enabled|status change) [0-9]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: precision = [0-9]+\.[0-9]+
usec$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: peer
([.0-9]{7,15}|[0-9a-fA-F:.]{4,39}) now (in)?valid$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjusting local clock by
-?[.0-9]+s$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjust time server -?[.0-9]+
offset$
Regards,
Tim Miller Dyck
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Wed Sep 5 10:09:31 2012
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64
(20110426)
KernLog: Sep 5 06:34:04 cmpsVMHost01 kernel: [271957.578288] SGI XFS with
ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
ProcEnviron:
LANGUAGE=en_CA:en
TERM=linux
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: ntp
UpgradeStatus: Upgraded to precise on 2012-08-25 (10 days ago)
** Affects: ntp (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug logcheck ntp precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1046340
Title:
ntp package missing logcheck exceptions file
/etc/logcheck/ignore.d.server/ntp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1046340/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1046340] Re: ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1046340 Title: ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1046340/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1046340] Re: ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046340 Title: ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1046340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046340] [NEW] ntp package missing logcheck exceptions file /etc/logcheck/ignore.d.server/ntp
Public bug reported:
Hello,
in Lucid, Package: ntp (1:4.2.4p8+dfsg-1ubuntu2) has the file
/etc/logcheck/ignore.d.server/ntp included. This is used to configure
logcheck to ignore ntp messages in syslog that are not error conditions.
However:
In Natty, this file is not present in the ntp package
In Oneric, this file is not present in the ntp package
In Precise, this file is not present in the ntp package
When logcheck is installed, all ntp syslog messages are raised as alerts
by logcheck because the ntp configuration file is not present.
It would be helpful to have /etc/logcheck/ignore.d.server/ntp included
with ntp packaging as with Lucid.
Here are sample contents based on the Lucid version with the addition of
status change tot he time sync line.
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: time reset
[+-]*[0-9]{1,2}\.[0-9]{6} s$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronisation lost$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: no servers reachable$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronized to
([0-9.]{7,15}|[0-9a-fA-F:.]{4,39}), stratum [0-9]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: synchronized to
LOCAL\([0-9]+\), stratum [0-9]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: kernel time sync
(disabled|enabled|status change) [0-9]+$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: precision = [0-9]+\.[0-9]+
usec$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: peer
([.0-9]{7,15}|[0-9a-fA-F:.]{4,39}) now (in)?valid$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjusting local clock by
-?[.0-9]+s$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ ntpd\[[0-9]+\]: adjust time server -?[.0-9]+
offset$
Regards,
Tim Miller Dyck
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Wed Sep 5 10:09:31 2012
InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64
(20110426)
KernLog: Sep 5 06:34:04 cmpsVMHost01 kernel: [271957.578288] SGI XFS with
ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
ProcEnviron:
LANGUAGE=en_CA:en
TERM=linux
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: ntp
UpgradeStatus: Upgraded to precise on 2012-08-25 (10 days ago)
** Affects: ntp (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug logcheck ntp precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046340
Title:
ntp package missing logcheck exceptions file
/etc/logcheck/ignore.d.server/ntp
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1046340/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883324] Re: False positive: Hidden file (symbolic link to directory) cannot be white-listed
Ran into this also. Thanks to reinhold for pointing to the patch.
I am just using the stock Ubuntu 12.04 version with the patch manually
applied. That is working fine for me in terms of avoiding the false
positive.
vi /usr/bin/rkhunter
At around line 846 and following
...
elif [ -d ${FNAME} ]; then
#
# For the ALLOWHIDDENFILE option we need to
allow
# a hidden symbolic link to a directory.
#
test ${OPT_NAME} = ALLOWHIDDENFILE -a -h
${FNAME} continue
case ${OPT_NAME} in
...
At around line 15102 and following (the change is just a comment)
...
FTYPE=`${FILE_CMD} ${FNAME} 2/dev/null | cat -v | tr -s '
' ' ' | cut -d' ' -f2-`
#jh - should include block special too.
#jh - also should cater for 'sticky directory' (like /tmp) when using file.
test -z ${FTYPE} -o -n `echo \${FTYPE}\ | egrep 'character
special|empty'` continue
...
Update the signature database as the rkhunter file signature has changed
with the edits above.
rkhunter --propupd
And here are the other configuration settings I needed to add to avoid false
positives on Ubuntu 12.04 Server.
vi /etc/rkhunter.conf
Avoid hidden directory/hidden file false positives
...
#
# Allow the specified hidden directories to be whitelisted.
#
# This is a space-separated list of directory pathnames.
# The option may be specified more than once. The option
# may use wildcard characters.
#
#ALLOWHIDDENDIR=/etc/.java
#ALLOWHIDDENDIR=/dev/.static
#ALLOWHIDDENDIR=/dev/.initramfs
#ALLOWHIDDENDIR=/dev/.SRC-unix
#ALLOWHIDDENDIR=/dev/.mdadm
## add /dev/.udev directory to avoid a false positive
ALLOWHIDDENDIR=/dev/.udev
#
# Allow the specified hidden files to be whitelisted.
#
# This is a space-separated list of filenames. The option may
# be specified more than once. The option may use wildcard
# characters.
#
#ALLOWHIDDENFILE=/etc/.java
...
#ALLOWHIDDENFILE=/usr/share/man/man5/.k5login.5.gz
## add /dev/.initramfs symbolic link to avoid a false positive
ALLOWHIDDENFILE=/dev/.initramfs
...
Avoid replaced by a script false positives
...
#
# Allow the specified commands to be scripts.
#
# This is a space-separated list of filenames. The option may
# be specified more than once. The option may use wildcard
# characters.
#
SCRIPTWHITELIST=/bin/egrep
SCRIPTWHITELIST=/bin/fgrep
SCRIPTWHITELIST=/bin/which
SCRIPTWHITELIST=/usr/bin/groups
SCRIPTWHITELIST=/usr/bin/ldd
SCRIPTWHITELIST=/usr/bin/lwp-request
SCRIPTWHITELIST=/usr/sbin/adduser
SCRIPTWHITELIST=/usr/sbin/prelink
## add /usr/bin/unhide.rb to avoid a false positive
SCRIPTWHITELIST=/usr/bin/unhide.rb
...
Regards,
Tim Miller Dyck
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883324
Title:
False positive: Hidden file (symbolic link to directory) cannot be
white-listed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/883324/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 942316] Re: Installing on Hyper-V doesn't launch
For those using 12.04 beta1 on Hyper-V, a workaround to the CD-ROM bug above (until beta 2 comes out) is to boot the initial installer with an additional kernel flag to not switch to using the Hyper-V IDE drivers. The boot flags can be viewed by pressing F5? F6? (one of those) on the setup boot screen and then navigating to the boot line with cursor keys and adding the boot parameter below before the double dash at the end of the line. The flag to disable the Hyper-V IDE drivers is: ata_piix.prefer_ms_hyperv=0 The CD-ROM install then proceeds as usual. Regards, Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/942316 Title: Installing on Hyper-V doesn't launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/942316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 953567] [NEW] lircd-0.9.0 reports USB disconnect followed by kernel Oops
Public bug reported: Hi, I had the following kernel Oops today, apparently related to lirc. I found some other bug reports stating that suspending the system can causes problems. However, the system was on the whole time, the remote was not in use and it was not manually unplugged. Ubuntu 11.10 lirc 0.9.0-0ubuntu1 kernel: linux-image-3.0.0-16-server3.0.0-16.29 Model of USB infrared receiver: I: Bus=0003 Vendor=1934 Product=5168 Version=0001 N: Name=Media Center Ed. eHome Infrared Remote Transceiver (1934:5168) P: Phys=usb-:00:1a.0-1.5 S: Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/rc/rc0/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=100013 B: KEY=fff 0 200108fc32e 2376051 0 700158000 41920001 9e9680 1000 B: MSC=10 syslog: Mar 12 18:55:00 mdVMHost01 lircd-0.9.0[862]: error reading from /dev/lirc0 (ret -1, expected 4) Mar 12 18:55:00 mdVMHost01 kernel: [1728244.384282] usb 1-1.5: USB disconnect, device number 4 Mar 12 18:55:00 mdVMHost01 lircd-0.9.0[862]: No such device Mar 12 18:55:00 mdVMHost01 kernel: [1728244.401242] BUG: unable to handle kernel NULL pointer dereference at 0050 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.402147] IP: [a015a6f7] show_protocols+0x107/0x150 [rc_core] Mar 12 18:55:00 mdVMHost01 kernel: [1728244.403058] PGD 39af08067 PUD 3872ea067 PMD 0 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.403973] Oops: [#1] SMP Mar 12 18:55:00 mdVMHost01 kernel: [1728244.404887] CPU 0 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.404900] Modules linked in: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs udf crc_itu_t ip6table_filter ip6_tables ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables tda18271 s5h1411 kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_realtek bridge stp ir_lirc_codec lirc_dev ir_sony_decoder saa7164 ir_jvc_decoder ir_rc6_decoder rc_rc6_mce ir_rc5_decoder mxm_wmi dvb_core ir_nec_decoder v4l2_common videodev i915 mceusb snd_hda_intel v4l2_compat_ioctl32 rc_core snd_hda_codec tveeprom drm_kms_helper snd_hwdep drm snd_pcm snd_timer wmi snd soundcore i2c_algo_bit mei(C) snd_page_alloc video lp parport raid456 async_pq async_xor xor async_memcpy async_raid6_recov usb_storage uas raid10 usbhid hid raid6_pq async_tx raid1 raid0 xhci_hcd e1000e r8169 multipath linear Mar 12 18:55:00 mdVMHost01 kernel: [1728244.413870] Mar 12 18:55:00 mdVMHost01 kernel: [1728244.415095] Pid: 4755, comm: cat Tainted: G C 3.0.0-16-server #28-Ubuntu Gigabyte Technology Co., Ltd. Z68A-D3H-B3/Z 68A-D3H-B3 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.417718] RIP: 0010:[a015a6f7] [a015a6f7] show_protocols+0x107/0x150 [rc_core] Mar 12 18:55:00 mdVMHost01 kernel: [1728244.419110] RSP: 0018:880026e11e08 EFLAGS: 00010202 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.420502] RAX: RBX: 8803e4d33000 RCX: 0001 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.421915] RDX: 8801eef28000 RSI: a015e180 RDI: 8803e4d332c0 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.423341] RBP: 880026e11e48 R08: R09: 4fb8 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.424789] R10: 0002 R11: 0246 R12: 8801eef28000 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.426246] R13: 8803e4d332c0 R14: 8803e4d33010 R15: 8803dc218b40 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.427731] FS: 7fec41411720() GS:8803ffc0() knlGS: Mar 12 18:55:00 mdVMHost01 kernel: [1728244.429248] CS: 0010 DS: ES: CR0: 80050033 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.430765] CR2: 0050 CR3: 0003da8ec000 CR4: 000426e0 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.432306] DR0: DR1: DR2: Mar 12 18:55:00 mdVMHost01 kernel: [1728244.433848] DR3: DR6: 0ff0 DR7: 0400 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.435378] Process cat (pid: 4755, threadinfo 880026e1, task 8803b224) Mar 12 18:55:00 mdVMHost01 kernel: [1728244.436925] Stack: Mar 12 18:55:00 mdVMHost01 kernel: [1728244.438449] 81c36240 a015e180 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.440025] 8803e84b9cd0 81851060 8803e4d33010 8803dc218b40 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.441616] 880026e11e78 813cd2b0 880026e11e68 8110e3de Mar 12 18:55:00 mdVMHost01 kernel: [1728244.443220] Call Trace: Mar 12 18:55:00 mdVMHost01 kernel: [1728244.444810] [813cd2b0] dev_attr_show+0x20/0x60 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.446410] [8110e3de] ? __get_free_pages+0xe/0x50 Mar 12 18:55:00 mdVMHost01 kernel: [1728244.448013] [811d7b06] fill_read_buffer.isra.7+0x66/0xf0 Mar 12 18:55:00 mdVMHost01 kernel:
[Bug 942256] Re: HyperV modules missing from -virtual flavor
Thanks Tim! I will retest when Beta 1 ships later this week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/942256 Title: HyperV modules missing from -virtual flavor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/942256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917135] Re: Hyper-V: enable all hv drivers and export them in the initramfs
Hi, I have success also with the -generic kernel image, but the -virtual kernel packages do not seem to include the hv_ drivers. Tested with linux-image-virtual 3.2.0.17.17 # dpkg -l | grep linux-image-virtual ii linux-image-virtual 3.2.0.17.17Linux kernel image for virtual machines # zcat /boot/initrd.img-3.2.0-17-virtual | cpio -it | grep hv_ lib/modules/3.2.0-17-virtual/kernel/drivers/hv/hv_utils.ko lib/modules/3.2.0-17-virtual/kernel/drivers/hv/hv_vmbus.ko 25562 blocks == Rebooted with the -generic kernel: # dpkg -l | grep linux-image-generic ii linux-image-generic 3.2.0.17.17Generic Linux kernel image # zcat /boot/initrd.img-3.2.0-17-generic | cpio -it | grep hv_ lib/modules/3.2.0-17-generic/kernel/drivers/hv/hv_utils.ko lib/modules/3.2.0-17-generic/kernel/drivers/hv/hv_vmbus.ko lib/modules/3.2.0-17-generic/kernel/drivers/net/hyperv/hv_netvsc.ko lib/modules/3.2.0-17-generic/kernel/drivers/scsi/hv_storvsc.ko 78921 blocks == Could the -virtual kernel packages get the same Hyper-V support? Thanks, Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917135 Title: Hyper-V: enable all hv drivers and export them in the initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/917135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 929545] Re: Hyper-V: PV Drivers for Ubuntu guests running on Hyper-V lose root device to ata_piix
Hi, The intention here is to boot every disk volume using the virtual Hyper-V SCSI adapter? That would be different than the procedure for setting up VM guest disks (on Windows systems only?) as described in Microsoft's Hyper-V docs, but maybe that is the goal. from http://technet.microsoft.com/en-us/library/dd183729%28WS.10%29.aspx You can select either integrated device electronics (IDE) or SCSI devices on virtual machines: IDE devices. Hyper-V uses emulated devices with IDE controllers. You can have up to two IDE controllers with two disks on each controller. The startup disk (sometimes referred to as the boot disk) must be attached to one of the IDE devices. The startup disk can be either a virtual hard disk or a physical disk. Although a virtual machine must use an IDE device as the startup disk to start the guest operating system, you have many options to choose from when selecting the physical device that will provide the storage for the IDE device. For example, you can use any of the types of physical storage identified in the introduction section. SCSI devices. Each virtual machine supports up to 256 SCSI disks (four SCSI controllers with each controller supporting up to 64 disks). SCSI controllers use a type of device developed specifically for use with virtual machines and use the virtual machine bus to communicate. The virtual machine bus must be available when the guest operating system is started. Therefore, virtual hard disks attached to SCSI controllers cannot be used as startup disks. ... Note Although the I/O performance of physical SCSI and IDE devices can differ significantly, this is not true for the virtualized SCSI and IDE devices in Hyper-V. Hyper-V. IDE and SCSI devices both offer equally fast I/O performance when integration services are installed in the guest operating system. I can try this early 12.04 code out too on a Hyper-V host. I am using Ubuntu 10.04 as a guest OS quite a bit on Hyper-V hosts. Regards, Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929545 Title: Hyper-V: PV Drivers for Ubuntu guests running on Hyper-V lose root device to ata_piix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/929545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930962] [NEW] dhcp3-server reports many bad udp checksums to syslog using virtio NIC
Public bug reported: Tested with dhcp3-server ver. 3.1.3-2ubuntu3.3 in Ubuntu 10.04.3 Server, x64. The DHCP server reports that UDP packets sent to it have bad checksums: Feb 11 06:57:18 ... dhcpd: 5 bad udp checksums in 5 packets Feb 11 06:58:22 ... dhcpd: last message repeated 7 times Feb 11 06:59:17 ... dhcpd: last message repeated 7 times The DHCP server host is a KVM virtual machine using a virtio-based virtual NIC. This problem has been reported for other distros using KVM and virtio: https://bugs.mageia.org/show_bug.cgi?id=1243 http://www.mail-archive.com/kvm@vger.kernel.org/msg41958.html - suggests using iptables to write in a checksum http://pkgs.fedoraproject.org/gitweb/?p=dhcp.git;a=blob;f=dhcp-4.2.2-xen-checksum.patch;h=038d346d726e131f1ab2579fe015a72b49733a0d;hb=HEAD - Fedora patch to dhcp to avoid this The simplest workaround is to change the virtual NIC type from virtio to Intel e1000 in KVM. Apparently this driver calculates checksums. But virtio is the default driver type. Thanks, Tim Miller Dyck ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: checksum dhcp3-server dhcpd kvm virtio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930962 Title: dhcp3-server reports many bad udp checksums to syslog using virtio NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/930962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368962] Re: Can't reboot kvm virtual machines using virsh
As acpid is required in guest VMs for the Upstart pre-stop procedure to work, I'd like to suggest that acpid be included by default in Ubuntu Server virtual machine variants (or all Ubuntu Server default installs, for that matter). This will enable this feature to automatically work as expected in future versions of Ubuntu Server. I submitted this suggestion here also: http://brainstorm.ubuntu.com/idea/28447/ Thanks, Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/368962 Title: Can't reboot kvm virtual machines using virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/368962/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 368962] Re: Can't reboot kvm virtual machines using virsh
As acpid is required in guest VMs for the Upstart pre-stop procedure to work, I'd like to suggest that acpid be included by default in Ubuntu Server virtual machine variants (or all Ubuntu Server default installs, for that matter). This will enable this feature to automatically work as expected in future versions of Ubuntu Server. I submitted this suggestion here also: http://brainstorm.ubuntu.com/idea/28447/ Thanks, Tim Miller Dyck -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/368962 Title: Can't reboot kvm virtual machines using virsh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/368962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693115] Re: arno-iptables-firewall 1.9.2.h-1 QoS script component has Bad substitution error with /bin/dash but not with /bin/bash
This has now been fixed upstream along with bash-isms in some of the other arno-iptables-firewall scripts. -Tim Miller Dyck Version 2.0.0b (March 25, 2011) --- ... ! remove bash-ism related to traffic-shaper plugin (Reported by Debian upstream, Debian bug #619496) ... See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619496 ** Bug watch added: Debian Bug tracker #619496 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619496 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693115 Title: arno-iptables-firewall 1.9.2.h-1 QoS script component has Bad substitution error with /bin/dash but not with /bin/bash -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693115] [NEW] arno-iptables-firewall 1.9.2.h-1 QoS script component has Bad substitution error with /bin/dash but not with /bin/bash
Public bug reported: Binary package hint: arno-iptables-firewall re: arno-iptables-firewall1.9.2.h-1 arno-iptables-firewall has a script that implements QoS -- it is at /usr/share/arno-iptables-firewall/plugins/60traffic-shaper.plugin. This script has an incompatibility with the default /bin/sh shell in Ubuntu (actually /bin/dash). An error “Bad substitution” is reported when the QoS script runs. Test case: vi /etc/arno-iptables-firewall/plugins/traffic-shaper.conf change to ENABLED=1 /etc/init.d/arno-iptables-firewall restart or /etc/init.d/arno-iptables-firewall status An error Bad substitution will be reported and the QoS script fails to run completely. As a workaround, switch the arno script to use /bin/bash. vi /usr/sbin/arno-iptables-firewall change the first line to#!/bin/bash instead of calling /bin/sh With this change, no error is reported and QoS is enabled as expected. I also tried the Ubuntu 10.10 version but had the same behavior. Thanks, Tim Miller Dyck --- Description:Ubuntu 10.04.1 LTS Release:10.04 arno-iptables-firewall: Installed: 1.9.2.h-1 Candidate: 1.9.2.h-1 Version table: *** 1.9.2.h-1 0 500 http://ca.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status ** Affects: arno-iptables-firewall (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/693115 Title: arno-iptables-firewall 1.9.2.h-1 QoS script component has Bad substitution error with /bin/dash but not with /bin/bash -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550369] Re: Hauppauge TV Card is detected as Leadtek IR in lucid
Hi TecnoBrat, Installing lirc-modules-source solved the problem, thanks! dkms automatically was called to compile and use all the lirc kernel modules included in the source package, including lirc_i2c. I was surprised this would work, as the package description for it says, Also, note that this package is not necessary for usage on Ubuntu since the modules are shipped in linux-ubuntu-modules. It is soley here in the case that a local patch needs to be applied. However, it appears the lirc_i2c.ko module included with the current kernel (2.6.32-23) is based on not the same source as is included in lirc-modules-source. r...@vmhost:/lib/modules# ls -la `find . -name lirc_i2c.ko` -rw-r--r-- 1 root root 21208 2010-06-11 08:02 ./2.6.32-23-server/kernel/ubuntu/lirc/lirc_i2c/lirc_i2c.ko -rw-r--r-- 1 root root 21176 2010-07-10 12:46 ./2.6.32-23-server/updates/dkms/lirc_i2c.ko I am now getting a warning from dkms that the built and installed versions are different of this module. r...@vmhost:/lib/modules# dkms status lirc, 0.8.6, 2.6.32-23-server, x86_64: installed (WARNING! Diff between built and installed module!) nvidia-current, 195.36.24, 2.6.32-23-server, x86_64: installed However, the newer module is still loaded and correctly detects the Hauppauge remote. Tim -- Hauppauge TV Card is detected as Leadtek IR in lucid https://bugs.launchpad.net/bugs/550369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550369] Re: Hauppauge TV Card is detected as Leadtek IR in lucid
I upgraded to Lucid today, including the lirc 0.8.6-0ubuntu4.1 update, and am still seeing this problem (mis-detection of a Hauppauge WinTV PVR-350 remote control as a Leadtek, the remote not working and lirc_dev taking 100% CPU). I am running the -server kernel if that makes a difference. Reverting back to the 2.6.31-22-server kernel fixes the problem for now. Anyone else seeing this? /var/log/syslog Jun 18 15:45:08 vmhost kernel: [ 10.633727] lirc_dev: IR Remote Control driver registered, major 61 ... Jun 18 15:45:08 vmhost kernel: [ 10.651169] bttv: driver version 0.9.18 loaded Jun 18 15:45:08 vmhost kernel: [ 10.651171] bttv: using 8 buffers with 2080k (520 pages) each for capture Jun 18 15:45:08 vmhost kernel: [ 10.663321] cx88/0: cx2388x v4l2 driver version 0.0.7 loaded Jun 18 15:45:08 vmhost kernel: [ 10.663482] lirc_i2c: chip 0x0 found @ 0x18 (Leadtek IR) Jun 18 15:45:08 vmhost kernel: [ 10.663484] lirc_dev: lirc_register_driver: sample_rate: 10 t...@vmhost:/lib/modules$ dpkg -l | grep lirc ii liblircclient0 0.8.6-0ubuntu4.1 infra-red remote control support - client library ii lirc 0.8.6-0ubuntu4.1 infra-red remote control support t...@vmhost:/lib/modules$ ls -la `find . -name lirc_dev.ko` -rw-r--r-- 1 root root 26168 2010-05-27 01:25 ./2.6.31-22-server/kernel/ubuntu/lirc/lirc_dev/lirc_dev.ko -rw-r--r-- 1 root root 27616 2010-06-03 19:26 ./2.6.32-22-server/kernel/ubuntu/lirc/lirc_dev/lirc_dev.ko -- Hauppauge TV Card is detected as Leadtek IR in lucid https://bugs.launchpad.net/bugs/550369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly
I see the fix is committed above, but the size='5G' hardcoding on line 37 of /usr/share/pyshared/VMBuilder/disk.py is still present in the current karmic version (python-vm-builder 0.11-0ubuntu2). Can this patch be merged into the karmic version? Thanks! -Tim -- python-vm-builder --raw doesn't set size correctly https://bugs.launchpad.net/bugs/303882 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 303882] Re: python-vm-builder --raw doesn't set size correctly
I see the fix is committed above, but the size='5G' hardcoding on line 37 of /usr/share/pyshared/VMBuilder/disk.py is still present in the current karmic version (python-vm-builder 0.11-0ubuntu2). Can this patch be merged into the karmic version? Thanks! -Tim -- python-vm-builder --raw doesn't set size correctly https://bugs.launchpad.net/bugs/303882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117227] Re: 2.6.20-15-generic kernel panic, cfq scheduler
This happened to me as well: a kernel panic with the last lines being EIP: [c01e9eb9] cfq_dispatch_insert+0x19/0xB0 SS:ESP 0068:e51b3 dec 0Kernel panic - not syncing: Fatal exception in interrupt This happened when using the cfq elevator and copying from a degraded raid 5 array to a separate larger single disk (non-raid). The fix for me was to use the deadline elevator. I have a photo of the screen if helpful also. Regards, Tim -- 2.6.20-15-generic kernel panic, cfq scheduler https://bugs.launchpad.net/bugs/117227 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126499] No devices listed in conf file were found due to mdadm RAID1 array UUID different from actual UUID reported by vol_id
Public bug reported: Early in the boot process for Feisty, I get a message from mdadm No devices listed in conf file were found When I read Bug #120504 (maybe this is a duplicate of that), I got a clue that the UUIDs in /etc/mdadm/mdadm.conf might not match the actual UUID. This was the case for two out of my four arrays. The other two arrays had blank UUIDs are reported by vol_id and started fine. The bug is is that mdadm and vol_id are reporting different UUIDs for the same device. # uname -a Linux atlas 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux # vol_id /dev/md0 ID_FS_USAGE=filesystem ID_FS_TYPE=ext3 ID_FS_VERSION=1.0 ID_FS_UUID=bff2d095-4504-4dcb-937a-c687422beadc ID_FS_LABEL=/boot ID_FS_LABEL_SAFE=boot # mdadm --detail /dev/md0 /dev/md0: Version : 00.90.03 Creation Time : Sun Jul 31 00:58:00 2005 Raid Level : raid1 Array Size : 979840 (957.04 MiB 1003.36 MB) Device Size : 979840 (957.04 MiB 1003.36 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Tue Jul 17 02:48:22 2007 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : f69e981b:39a7f096:c5346ca4:0f25f4c2 Events : 0.11860 Number Major Minor RaidDevice State 0 2210 active sync /dev/hdc1 1 311 active sync /dev/hda1 # ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 9 2007-07-17 02:29 3d721ac2-b42f-4f53-ba48-63828d30013e - ../../md4 lrwxrwxrwx 1 root root 28 2007-07-17 02:29 630f92e4-3406-42ee-982f-9abdb9696a4f - ../../mapper/vg_root-lv_root lrwxrwxrwx 1 root root 10 2007-07-17 02:29 a3150b2e-5416-4052-901f-f17bb8affc4f - ../../sdc1 lrwxrwxrwx 1 root root 9 2007-07-17 02:29 bff2d095-4504-4dcb-937a-c687422beadc - ../../md0 # mdadm --detail --scan ARRAY /dev/md0 level=raid1 num-devices=2 UUID=f69e981b:39a7f096:c5346ca4:0f25f4c2 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6b73608b:f42d5d48:c5346ca4:0f25f4c2 ARRAY /dev/md2 level=raid1 num-devices=2 UUID=711d6d5c:dc49dd88:c5346ca4:0f25f4c2 ARRAY /dev/md4 level=raid1 num-devices=2 UUID=8e449434:a93efdbf:c5346ca4:0f25f4c2 # vol_id -u /dev/md0 bff2d095-4504-4dcb-937a-c687422beadc # vol_id /dev/md1 ID_FS_USAGE=raid ID_FS_TYPE=LVM2_member ID_FS_VERSION=LVM2 001 ID_FS_UUID= ID_FS_LABEL= ID_FS_LABEL_SAFE= # vol_id /dev/md2 ID_FS_USAGE=other ID_FS_TYPE=swap ID_FS_VERSION=2 ID_FS_UUID= ID_FS_LABEL= ID_FS_LABEL_SAFE= # vol_id /dev/md4 ID_FS_USAGE=filesystem ID_FS_TYPE=ext3 ID_FS_VERSION=1.0 ID_FS_UUID=3d721ac2-b42f-4f53-ba48-63828d30013e ID_FS_LABEL=data ID_FS_LABEL_SAFE=data Since the recommended method to create mdadm.conf is through appending the output of mdadm --detail --scan, if mdadm isn't getting UUIDs the same way vol_id is, problems result. I started having this problem after upgrading to Feisty. In my case, my arrays did start OK even with this error because (I think) they are type FD and the kernel was able to start them by itself. This occurs with: mdadm 2.5.6-7ubuntu5 volumeid 108-0ubuntu4 mdadm superblock versions are .90. Perhaps this bit from the mdadm man page is relevant: For version-0.90 superblocks part of the SHA1 hash of the hostname will be stored in the later half of the UUID. I haven't tried updating the UUID with mdadm --update. I'm not sure if this can be done without losing the array. FIX: Manually editing the UUIDs in /etc/mdadm/mdadm.conf to match those from vol_id fixes the mdadm error on boot and allows it to find all its devices. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New -- No devices listed in conf file were found due to mdadm RAID1 array UUID different from actual UUID reported by vol_id https://bugs.launchpad.net/bugs/126499 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126499] Re: No devices listed in conf file were found due to mdadm RAID1 array UUID different from actual UUID reported by vol_id
Regarding the fix, after updating mdadm.conf, one also needs to regenerate the initrd.img files: update-initramfs -k all -u -- No devices listed in conf file were found due to mdadm RAID1 array UUID different from actual UUID reported by vol_id https://bugs.launchpad.net/bugs/126499 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64632] Workaround for Re: mga-vid-source fails to compile
I also saw this when trying to install the module using the edgy version. The problem, identified in the Debian upstream bug reports, is that the edgy version is old and doesn't compile on the edgy kernel. The fix is to use the latest (feisty) version, which has the fixes. Here's what worked for me: Install mga-vid-common from the normal edgy repository (avoids a libc dependency in the fiesty version) Download, compile and install the latest feisty mga-vid-source. You can ignore the old README directions and use the Debian module tools to make the module. e.g. wget http://mirrors.kernel.org/ubuntu/pool/universe/m/mga-vid/mga-vid-source_1.55-1.2_i386.deb dpgk -i mga-vid-source_1.55-1.2_i386.deb cd /usr/src m-a update,prepare m-a a-i mga-vid depmod -a # test it out modprobe mga_vid tail /var/log/syslog Dec 19 20:33:28 atlas kernel: [ 349.105711] Matrox MGA G200/G400/G450/G550 YUV Video interface v2.01 (c) Aaron Holtzman A'rpi Dec 19 20:33:28 atlas kernel: [ 349.105746] mga_vid: Found MGA G400/G450 at :01:00.0 Dec 19 20:33:28 atlas kernel: [ 349.105814] mga_vid: MMIO at 0xf605 framebuffer: 0xE200 Dec 19 20:33:28 atlas kernel: [ 349.105829] mga_vid: OPTION word: 0x50044120 mem: 0x10 SGRAM Dec 19 20:33:28 atlas kernel: [ 349.105839] mga_vid: detected RAMSIZE is 32 MB Dec 19 20:33:28 atlas kernel: [ 349.105847] mga_vid: 1 supported cards found Dec 19 20:33:28 atlas kernel: [ 349.105986] mga_vid: using major: 83 (assigned or default!) # all is good The only issue I found is that the 1.55-1.2 module creates its device as /dev/mga_vid0 rather than the /dev/mga_vid that mga_vid_test and mplayer expect. I added this line to /etc/modutils/mga-vid-common to fix that issue: post-install mga_vid ln --force -s /dev/mga_vid0 /dev/mga_vid One last thing is that I found the output of mga_vid_test garbled when I ran it at a text-mode console but when I used a framebuffer console (e.g. vga=0x305 in the kernel boot parameter line), the Matrox output was correct. It also worked with mplayer as expected (which was the desired end-result). Regards, Tim -- mga-vid-source fails to compile https://launchpad.net/bugs/64632 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 39767] Fixed -- Re: /etc/init.d/asterisk script does not stop safe_asterisk correctly if asterisk is not running
Thanks Ante! I extracted and tested the 1.2.13~dfsg-2ubuntu2 init script and it works great. It's a nice feeling to see a patch applied. -Tim -- /etc/init.d/asterisk script does not stop safe_asterisk correctly if asterisk is not running https://launchpad.net/bugs/39767 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46688] Re: asterisk init.d script stop command fails when $RUNASTSAFE = yes
It is fixed, and thanks! -Tim -- asterisk init.d script stop command fails when $RUNASTSAFE = yes https://launchpad.net/bugs/46688 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
