@Alejandro Miranda I've noticed the command moves the sound from the top
speakers to the bottom. Sounds, no doubt, but seems to disable to
speakers up top.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
There was a question posted about this issue here:
https://answers.launchpad.net/ubuntu/+question/105987
I purchased a separate bluetooth dongle and was able to get my keyboard
to sync by logging in from another computer and pairing the keyboard
with the other dongle. The disadvantage of using t
No "bluetooth" file in the /etc/default directory -- not sure where the
file went but assuming this would mean default values were used. Will
check later today whether restoring the file brings back the pre-Lucid
functionality.
--
Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anym
Problem is back on Lucid -- unplugging and replacing doesn't fix it
anymore -- I will check to see if the HID2HCI_ENABLED setting has
changed.
--
Bluetooth Logitech Dinovo Edge Keyboard/Mouse dones not work anymore
https://bugs.launchpad.net/bugs/269851
You received this bug notification because
I have been experiencing freezes as well -- many/most of them
accompanied by a blinking caps lock.
I run the latest updates of Jaunty on a Lenovo x301. I do not run ext4
either. I have been able to avoid freezes by turning off the wireless
devices (including both bluetooth and wifi via the physi
I have had this problem ever since I started using a TV as a display
(DVI to HDMI cable from an nVidia 9600GT). Although I never checked the
DPI reported by X in Intrepid, I did have the huge GDM, Etherape and
Google Earth fonts. For most other apps, I can usually able to change
application setti
I tried Jaunty last week and can confirm that the problem exists on
2.6.28 as well. Something was broken in Intrepid.
For more detail, the connection between the dongle and the keyboard
remains/resumes after rebooting. I can navigate BIOS fine and have no
problem navigating the boot menu when I
I am having new problems with my diNovo as well - I think it may have
something to do with a difference in the way that the dongle is being
recognized and initialized during startup because I am able to get it to
work if I follow these steps:
(1) unplug the dongle from the USB slot,
(2) plug the
Thanks, Michael (and Bernd). Confirming that adding "large-memory" to
lilo.conf does resolve the issue for me.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Thanks for the link, Bernd.
Yes, I am running lilo.
It is worth noting that the file I've been using since building my
kernel (shows up as 2.6.24.3) is actually quite large. It probably
shouldn't be, but even the 2.6.22 files are over 8 megabytes:
-rw-r--r-- 1 root root 8564557 2008-04-18 00:5
I compiled a custom 2.6.24 kernel to get around the "bad gzip magic
numbers" problem I was having. Unfortunately, I still can not use 3d
acceleration or sound with this new compiled kernel - I guess I'll be
watching for 2.6.24-17 generic. Hardy releases in 3-days ... really?
I am leaving this th
In my test, 2.6.22 was re-created fine.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Thanks for the suggestion. "pci=nomsi" does not work for me. I am
going to try generating a new 2.6.22 image to see if that works (I don't
think I have created a 2.6.22 since the move to hardy) - this should
tell me whether the problem is in creating the images or if the problem
is in loading the
Confirmed the problem still exists for me on 2.6.24-16.
"checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd"
Nobody else seems to be getting the above message -- I am attaching my
image to this comment.
For more information, the machine is a Core2 Duo and
I am also experiencing difficulties booting 2.6.24-15.
ASUS P5K-E with 3 SATA drives in RAID-1 containing root and boot.
2.6.22-14 (and lower) boot fine. I have tried 2.6.24-12 through
2.6.24-15 and always get the following message:
"checking if image is initramfs...it isn't (bad gzip magic numb
I agree that it is possible (likely even) that the comments here reflect
several problems and not just one. As an end-user, I report on symptoms
as best I can (i.e. "wont boot after kernel update"), the underlying
problems are probably better identified by those more familiar with the
structure of
I get it too: xgl+x64 and restricted nVidia
--
Certain processes show incorrect memory usage when using xgl
https://bugs.launchpad.net/bugs/148325
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-
Problem solved (again)
I used the liveCD from Gutsy to boot, and re-assembled the array using
info from this page:
http://ubuntuforums.org/showthread.php?t=408461
mounted the volume and then ran lilo following some information I found
here:
http://www.syrlug.org/contrib/boot-loaders.html#LI
I am wondering if my bug #107249 is also being caused by this. In my
case, kernel updates have sometimes failed and have resulted in the
system presently being unbootable.
My machine, an Asus A8V, reports 4 sata drives, two on each controller.
Three of these drives are being used by linux: a boot
Over the weekend some process caused me to need to reboot the machine -
which is a problem because the machine "doesn't have a valid boot
signature" as of the last kernel update. This is the third time a
failed semi-automatic kernel update has left the computer unusable (I
typically accept kernel
The latest kernel update has failed. This time the message that I
receive is "Fatal: First sector of /dev/sda1 doesn't have a valid boot
signature". This does not appear to have anything to do with the RAID -
mdstat shows all volumes are up:
Personalities : [raid1] [raid6] [raid5] [raid4]
m
So I added sdc1 back to the md0 array. This was enough to get me past
the errors in the upgrade and everything checks out ok. I guess I'll
really know when I next try to reboot.
It is not clear to me why sdc1 was dropped from the array ... I will
look for a log to see if I can find an explanatio
i think this has something to do with my RAID, for whatever reason.
"cat /proc/mdstat" produces the following output, suggesting md0 is not
fully functional.
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sdc2[0] sdb2[2] sdd2[1]
468856832 blocks level 5, 64k chunk,
With the last kernel update, I think I've encountered the problem again.
My guess is that this machine will not be able to reboot so I hope to
keep it running for long enough to provide any log files that might be
related. To start with, I'm attaching a screenshot which shows the
error message.
*
The latest kernel update worked fine so I am assuming that the problem
no longer exists. This report should be closed.
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I have re-installed using the release version.
I did save all of the contents from my /var/log directory so any files
that would have been there are still available.
Also - I recovered my firefox session where I was searching for an
answer after the upgrade failure and before the reboot. The str
the /var/log/dist-upgrade directory is empty.
BTW: mounted md0 by the following steps:
installed mdadm (not positive this was necessary)
created directory /mnt/md0
typed "sudo mount -t auto /dev/md0 /mnt/md0"
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/
Right now I don't have access to md0 which contains that directory. If
I could install RAID support after booting from the live CD, then I
might be able to access these files.
--
failed kernel update followed by boot failure
https://bugs.launchpad.net/bugs/107249
You received this bug notificati
I expect to install the release version of Feisty tomorrow evening -
I've decided that having a running system is far more important than
preserving the configuration data stored on /etc/openvpn, /etc/apache2,
and /var (addressing the repair/restore install issue). However, I
still fear that the u
** Description changed:
I installed feisty from the 4/14/07 alternate CD (to support software
RAID) and was able to boot thanks to the fix to bug #103177.
The system worked fine for a day or so - then the update manager
provided kernel 2.6.20-15, which was not able to install (not sure
** Description changed:
I installed feisty from the 4/14/07 alternate CD (to support software
- RAID) and was able to boot thanks to the fix to bug #103177:
-
- https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/103177
+ RAID) and was able to boot thanks to the fix to bug #103177.
The
Public bug reported:
I installed feisty from the 4/14/07 alternate CD (to support software
RAID) and was able to boot thanks to the fix to bug #103177:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/103177
The system worked fine for a day or so - then the update manager
provided kernel 2
I believe I am having this same problem.
My machine contains 4 sata drives, 3 of which are being used for linux,
configured as two RAIDs:
md0: RAID1:
/
md1: RAID5: LVM:
/home
/tmp
swap
The above configuration worked well in Edgy, but I didn't have access to
my wireless ethernet (WPA
33 matches
Mail list logo
