** Changed in: kvm (Ubuntu)
Status: Fix Committed => In Progress
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Changed in: qemu (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: Fix Committed => Confirmed
** Changed in: kvm (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: In Progress => Confirmed
--
Could not open /proc/bus/usb/d
** Changed in: network-manager-applet (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: network-manager-applet (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: In Progress => Confirmed
--
nm-applet crashed with SIGSEGV in gtk_combo_box_
Public bug reported:
On TWO separate Asus A7N266-VM motherboards, installing Feisty or
running it from the Live CD, there is no sound output. Both have line-
out connected to the LCD monitor speakers. Both work correctly with
Windows XP or Windows 2003.
These systems have Nvidia nForce chip-sets
Okay, scratch this! It turns out that:
1) I had forgotten to turn the amplifier on for the 2nd system!
2) Despite what the manual says, these motherboards require jumpers to feed
line-out to the rear socket
3) The 1st system was missing these jumpers, the 2nd had them.
I've attached photographs
I've got the same problem here. Bluetooth printing to HP Deskjet 995C
was working fine earlier in the Gutsy release cycle but tonight I find
it can't print and the reason appears to be related to the appamor
configuration in /etc/appamor.d/usr.sbin.cupsd since disabling appamor
(sudo /etc/init.d/ap
I found a comment that seems strongly related to this in bug #139665 by
Martin Pitt:
https://bugs.edge.launchpad.net/ubuntu/+source/cupsys/+bug/139665/comments/2
Which seems to suggest the issue isn't strictly appamor but cups trying
to access /dev/tty inappropriately.
--
[Gutsy] : bluetooth pr
Martin's comment about /dev/tty and cupsd seems related to an issue I've
recently experienced and attached a report to bug #147800 "...bluetooth
printing was working but is not..."
Disabling appamor provided a work-around in that case but I'd like to
sort the issue out with appamor or cupsd.
--
In the latest Gutsy kernel images (looking at 2.6.22-13 here) vesafb is
no longer compiled into the kernel image as it was when this bug was
first reported. This is the reason the previous work-around no longer
works.
As MOM has reported, it is now necessary to remove the vesafb module
blacklist,
It is working correctly here for x86_64 with nvidia-glx-new on Nvidia
GeForce Go 7600.
--
GDM Startup Fails With Accessible login
https://bugs.launchpad.net/bugs/107383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
I think the issue was caused by bug #143958 that Colin and I solved
earlier in the Gutsy development cycle. A similar issue occurred on a
laptop using the Alternate installer. I'll try to test this out on a
server over the next few days.
--
Feisty LiveCD: Unable to find a medium containing a live
It does look as if this bug has returned. I'll dig into it.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Incomplete => Confirmed
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work af
I've been seeing this problem with Alt+Tab and Shift+Alt+Tab for the
last 2-3 weeks of the Gutsy development cycle but only just bothered to
research it. The gconf apps/metacity/global_keybindings/switch_windows*
edits fixed it, although compiz is running by default.
It *may* have been caused by s
I was just thinking earlier about how to further debug this. The
problem is still present with the final release updates.
--
gnome-terminal resize legend displayed as blocks when Compiz is enabled
https://bugs.launchpad.net/bugs/145604
You received this bug notification because you are a member
Sometimes it helps to engage brain before putting mouth into gear!
In my edd module-build instructions above I forgot two things:
1. libx86 is for user-space applications; no involvement in the kernel (was
thinking about vbetool at the time I typed that!)
2. The built module can't be modprobe-d
If you're feeling particularly adventurous you could build the kernel
EDD module.
1. Install the kernel-source from GIT
(https://wiki.ubuntu.com/KernelGitGuide) or use
$ sudo apt-get install linux-source
$ sudo tar -xjf linux-source-2.6.22.tar.bz2
$ cd /usr/src/linux-source-2.6.22
2. Edit debian
A follow-up to my observations of the SCSI address allocation. It looks
as if this is determined in
drivers/ata/libata-core.c::ata_host_register()
where, in part, you find "/* print per-port info to dmesg */"
and in turn calls
drivers/ata/libata-scsi.c::ata_scsi_scan_host()
It appears that ea
Mikel, thanks for those reports, they help clarify your circumstances
tremendously. This is just off the top of my head without any real
investigation, but the difference in the SCSI addresses between Windows
and Linux makes me wonder about how the SCSI addressing is being
determined.
For Windows,
Will all those experiencing this bug with Gutsy give us detailed
information as to the physical configuration of the motherboard disk
interfaces and disk drives so we can understand the precise
circumstances that cause this?
Right now we have a combination of comments, some of which indicate an
is
Robert, the solution to your issue is to edit /boot/grub/menu.lst and
set groot correctly. This is what is used when the kernel is updated.
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You recei
Robert, the entries in menu.lst inside the
### BEGIN AUTOMAGIC KERNELS LIST
section that begin with a single comment # are actually used by the
updater as settings.
Genuine comments use two ## symbols, just to confuse you.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/
Public bug reported:
Binary package hint: update-manager
Gutsy 32-bit installed from Alternate CD iso (20070921.1) into a 32-bit
kvm/qemu guest image (kvm-44 + kvm-intel).
>From the update-notifier Update Manager is offering x64_64 kernel image
and headers updates on a 32-bit installation. I'll
** Attachment added: "Update-Manager offering x86_64 kernel packages"
http://launchpadlibrarian.net/9478564/updates.png
--
x86_64 kernel image updates offered on x86 (i386)
https://bugs.launchpad.net/bugs/144516
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hmm, it must be tiredness! After staring at the screenshot I noticed it
says "x86/x86_64" - I had been reading it as "x86_64"!
I bet if I let it install (which I wasn't doing because I thought it was
wrong!) it'll be okay. Will confirm that shortly.
--
x86_64 kernel image updates offered on x86
** Attachment removed: "Correct acpi-rsdp_scan behaviour"
http://launchpadlibrarian.net/9471399/acpi-rsdp.diff
** Attachment added: "Correct acpi-rsdp_scan behaviour"
http://launchpadlibrarian.net/9496406/acpi-rsdp.diff
** Attachment removed: "Correct acpi-rsdp_scan behaviour"
http://
** Attachment added: "Correct acpi-rsdp_scan behaviour"
http://launchpadlibrarian.net/9496421/acpi-rsdp.diff
--
ACPI acpi_scan_rsdp() breaks some PCs by not honouring ACPI specification
https://bugs.launchpad.net/bugs/144336
You received this bug notification because you are a member of Ubunt
** Attachment removed: "Correct acpi-rsdp_scan behaviour"
http://launchpadlibrarian.net/9496421/acpi-rsdp.diff
** Attachment added: "Correct acpi-rsdp_scan behaviour"
http://launchpadlibrarian.net/9499097/acpi-rsdp.diff
--
ACPI acpi_scan_rsdp() breaks some PCs by not honouring ACPI speci
usr/bin/nm-applet
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.6.5-0ubuntu9
PackageArchitecture: amd64
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/tj
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_GB.UTF-8
SHELL=/bin/bash
*** This bug is a duplicate of bug 124336 ***
https://bugs.launchpad.net/bugs/124336
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/9511709/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/9511710/Dependencies.txt
** Attachment added:
ntu 7.10
ExecutablePath: /usr/bin/nm-applet
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.6.5-0ubuntu9
PackageArchitecture: amd64
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/tj
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/
Confirmed. I thought it was my imagination but since an update about a
week ago (so, around 20th September 2007) gnome-power-manager doesn't
hibernate the PC when battery level gets to critical. This had been
working fine up to then and was in regular use.
I did a manual hibernate test from a fres
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/9512791/Xorg.0.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
Public bug reported:
Binary package hint: xserver-xorg
Gutsy 32-bit LiveCD Beta (20070925.2) on Sony Vaio SRX51P with Intel
i810 video.
When GDM starts the backlight is lit but no display. Able to switch to
VT consoles (which are displayed and are interactive) and back. Using
"ps" and checking l
** Attachment added: "kern.log"
http://launchpadlibrarian.net/9512792/kern.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
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-
This shows the video detection process
** Attachment added: "casper.log"
http://launchpadlibrarian.net/9512805/casper.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
** Attachment added: "Original non-display xorg.conf"
http://launchpadlibrarian.net/9512868/xorg.conf.20070926084629
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Doing a further
$sudo dpkg-reconfigure xserver-xorg
And choosing the "Advanced" monitor configuration option I set:
Horizontal Frequencies: 28-64
Vertical Frequencies: 43-60
Resolutions: 1024x768
Colour Depth: 24
When started, GDM correctly uses the entire LCD panel and
1024x768x24bpp.
Attachi
** Attachment added: "Working session Xorg.0.log"
http://launchpadlibrarian.net/9512873/Xorg.0.log
--
LiveCD No intel video
https://bugs.launchpad.net/bugs/145128
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: ubiquity
Gutsy 32-bit LiveCD Beta (20070925.2) Install.
Choosing manual partitioning and assigning /boot /home and swap to pre-
existing (Feisty-created) partitions, the installer refuses to proceed
unless /boot is formatted.
This is clearly impossible
Yes, it was misleading (if you don't read and *think* about it carefully!) but
ultimately it installed the correct 32-bit updates.
Maybe I was confused by it more because I'm heavily into 64- and 32-bit
development work and always having to double-check which target I'm building
for.
--
x86_64
Finally got to test Gutsy 32-bit Beta (20070925.2) on Sony Vaio SRX51P
since the unionfs bug is (almost) sorted - the PC started albeit a few
problems still reported for unionfs.
However, the Lucent WaveLan/IEEE version 01.01 mini-pci card that is
interfaced via the pccard interface and works fine
Public bug reported:
Binary package hint: casper-udeb
Gutsy Desktop CD i386 32-bit Beta (20070925.2).
Loading on Sony Vaio SRX51P initial keyboard layout (consoles and xorg)
is US, not GB (UK), meaning " and @, # and £ and maybe others are
transposed.
** Affects: casper (Ubuntu)
Importance
Well, the issue has recurred today. I had been using it without Cross-
fader. Before a PC restart I re-enabled Cross-fader in Rhythmbox.
After the restart Rhythmbox is back to using a large amount of CPU and
pushing the temperatures up. I tried disabling the plug-ins, one-
at-a-time, but with them
Confirmed with Gutsy x86_64. Set desktop effects to "None" in gnome-
appearance-properties "Visual Effects" tab. Compiz stopped immediately.
Next time logging in realised Compiz is running, cube is active, *but*
gnome-appearance-properties "Visual Effects" tab shows "None".
** Changed in: gdm (Ub
Public bug reported:
Binary package hint: compiz
Gutsy x86_64.
Whilst Compiz is enabled if a gnome-terminal window is drag-resized the
legend displaying the size during dragging is displayed as blocks rather
than numbers.
When Compiz is disabled the resize legend appears correct.
** Affects: c
** Attachment added: "gnome-terminal resize legend showing blocks"
http://launchpadlibrarian.net/9529204/gnome-terminal-resize.png
--
gnome-terminal resize legend displayed as blocks when Compiz is enabled
https://bugs.launchpad.net/bugs/145604
You received this bug notification because you a
Sebastien, in my case definitely gnome-appearance-manager.
--
Compiz not disabled by gnome-appearance-properties
https://bugs.launchpad.net/bugs/137941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Seems more applicable to nm-applet since it is responsible for managing
the keys.
** Summary changed:
- [Gutsy] Unable to connect to WPA2 if the AP was previously using WPA
+ [Gutsy] Unable to connect to Access Point if encryption method (WEP/WAP/WAP2)
of the AP is changed
** Also affects: netw
** Bug watch added: GNOME Bug Tracker #481181
http://bugzilla.gnome.org/show_bug.cgi?id=481181
** Also affects: rhythmbox via
http://bugzilla.gnome.org/show_bug.cgi?id=481181
Importance: Unknown
Status: Unknown
--
CPU 60% and High Temperatures with Cross-Fader and low bit-rate MP
** Summary changed:
- CPU 60% and High Temperatures playing large MP3s
+ CPU 60% and High Temperatures with Cross-Fader and low bit-rate MP3
--
CPU 60% and High Temperatures with Cross-Fader and low bit-rate MP3
https://bugs.launchpad.net/bugs/141390
You received this bug notification because yo
Public bug reported:
Binary package hint: linux-source-2.6.22
Gutsy x86_64 with kernel 2.6.22-12-generic.
Up until a recent kernel update hibernate (and suspend) was working
fine. However, since the update hibernate seems to freeze the PC (in
/etc/acpi/hibernate.sh) at the point where it does:
This is the kern.log of a successful hibernate. GDM was stopped whilst
at the greeter stage after a cold boot.
** Attachment added: "Successful hibernate kern.log"
http://launchpadlibrarian.net/9529407/kern.log
--
Hibernate freezes PC before writing disk image
https://bugs.launchpad.net/bugs/
This is the output of /etc/acpi/hibernate.sh captured for the successful
hibernate action in the previous comment. It was captured by adding "set
-x" to the top of /etc/acpi/hibernate.sh and doing:
$ sudo su
$ /etc/acpi/hibernate.sh force 2>&1 | tee /var/log/hibernate.log
** Attachment added: "Su
This is the kern.log of an unsuccessful hibernate, captured using an
ACPI_DEBUG/PM_DEBUG kernel build.
** Attachment added: "Unsuccessful hibernate DEBUG kern.log"
http://launchpadlibrarian.net/9529424/kern-debug.log
--
Hibernate freezes PC before writing disk image
https://bugs.launchpad.net
This is the output of /etc/acpi/hibernate.sh captured for the
unsuccessful hibernate action in the previous comment, using an
ACPI_DEBUG/PM_DEBUG kernel. It was captured by adding "set -x" to the
top of /etc/acpi/hibernate.sh and doing:
$ sudo su
$ /etc/acpi/hibernate.sh force 2>&1 | tee /var/log/
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
--
Hibernate freezes PC before writing disk image
https://bugs.launchpad.net/bugs/146196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
This is the kern.log of a successful hibernate with the
ACPI_DEBUG/PM_DEBUG kernel.
The PC was started from cold, and GDM stopped before log-in. the
hibernate was then activated manually:
$ sudo su
$ /etc/acpi/hibernate.sh force 2>&1 | tee /var/log/hibernate.log
** Attachment added: "Successful
This is the output of /etc/acpi/hibernate.sh captured for the successful
hibernate action in the previous comment, using an ACPI_DEBUG/PM_DEBUG
kernel. It was captured by adding "set -x" to the top of
/etc/acpi/hibernate.sh and doing:
$ sudo su
$ /etc/acpi/hibernate.sh force 2>&1 | tee /var/log/hi
*** This bug is a duplicate of bug 73744 ***
https://bugs.launchpad.net/bugs/73744
** Changed in: rhythmbox
Bugwatch: GNOME Bug Tracker #481181 => GNOME Bug Tracker #385061
** This bug has been marked a duplicate of bug 73744
rhythmbox is slow!
--
CPU 60% and High Temperatures with
Trying to build the suspend package utility s2ram on Feisty 32-bit I
also ran into this problem. Based on what other people had said I
believed initially it was a bug in the pciutils package, and libpci in
particular.
After considerable hacking about between the configure scripts and
Makefiles of
I believe the FE31 model range is similar to the FE41 range; I have an
FE41Z and met the same issue. The root cause is that these models do not
use sonypi mechanisms. Instead they appear (from examining Windows Vista
Device Manager) to be using Sony NC (Notebook Control).
The smartdimmer comand-li
Public bug reported:
Binary package hint: linux-source-2.6.20
Feisty 32-bit (and 64-bit) on Sony Vaio VGN-FE41Z.
The screen backlight is not turned on after suspend/resume. Suspend to
RAM or disk has the same result. I've been doing a variety of tests
trying to narrow down the cause.
I've tried
The hash in drivers/base/power/resume.c is in the resume() function
itself, and doesn't appear to give a clue as to what caused the error.
After un-blacklist-ing ipw3945:
Magic number: 7:598:216
hash matches device ttyu0
I've no idea what physical device this is! It could be the Alps
Glidepad, o
Attached is a tar.gzip file containing two files:
1) kern.log covering a suspend/resume cycle
2) VGN-FE41Z-resume.log containing the output of:
uname -a
lspci -vv
lspci -vvn
dmidecode
** Attachment added: "VGN-FE41Z-resume.log.tar.gz"
http://librarian.launchpad.net/7773149/VGN-FE41Z-resume.l
In case it's of any use I'm attaching the DSDT of the R0200J3 BIOS
generated using:
$ sudo cat /proc/acpi/dsdt > VGN-FE41Z-R0200J3-DSDT.bin
** Attachment added: "VGN-FE41Z-R0200J3-DSDT.bin.tar.gz"
http://librarian.launchpad.net/7773171/VGN-FE41Z-R0200J3-DSDT.bin.tar.gz
--
Resume failure: Fei
I have experienced the same error on Feisty with Wine, trying to execute
a Windows executable from an xTerm:
$ ./PHBSYS-01101528-UN.exe
Can't exec "/usr/bin/wine-auto": No such file or directory at
/usr/share/binfmt-support/run-detectors line 103.
run-detectors: warning: unable to exec /usr/bin
I don't share your perceptions of smartdimmer's effect, it seems correct
to me. Having looked at the source-code, and that of nvclock (recently
updated and does brightness and more) I know that both are directly
controlling the Nvidia chipset screen brightness registers.
As to the Fn keys, yes it
Problem likely caused by incorrectly configured RAM modules
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Needs Info => Unconfirmed
--
<3>BUG: soft lockup detected on CPU#1!
https://bugs.launchpad.net/bugs/63165
You received this bug notification because you are a member of Ubuntu
B
This issue still affects Feisty running stock installations of samba.
The issue is in samba but affects QEMU.
It appears the issue is that the samba packages for Debian/Ubuntu are
compiled with the fhs.patch applied, which prevents samba from using a
private secrets directory.
There has been ongo
This is a known issue upstream with debian samba package patches
** Changed in: samba (Ubuntu)
Status: Rejected => Confirmed
--
samba can't be launched by a normal user (qemu related)
https://bugs.launchpad.net/bugs/50385
You received this bug notification because you are a member of Ubun
I had assumed it had to be started manually, but it does make sense to
have it start with the session. I've added it as you suggest and would
recommend it be added during package installation to help novice users
especially - bluetooth isn't the best explained or understood
application right now so
This bug is still outstanding in Feisty, for bluetooth:// URIs at least.
Is there something we can do to get it sorted out?
--
GUI does not accept all URL schemes accepted by CUPS itself
https://bugs.launchpad.net/bugs/9373
You received this bug notification because you are a member of Ubuntu
Bug
...continued... (apologies for the mispost above - accidentally hit the
Submit button via an over-sensitive glidepad!)
"argument 2" turns out to be the compiler define VERSION, which is 0.31.
However, argument 2 to gnome_program_init() is a const char *
VERSION is defined twice in config.h, on li
Additional issues:
1. After "sudo make install" various Printer Manager dialog box tabs are
missing or incomplete, and options such as Remove Printer are
unavailable.
2. Trying to repair using "sudo apt-get --reinstall install gnome-cups-
manager" doesn't fix (1)
3. "sudo make uninstall" returns
Update: A fix for the VERSION type issue is to change configure.in, line
2, to:
AC_INIT(gnome-cups-manager, "0.31")
--
Building gnome-cups-manager source fails
https://bugs.launchpad.net/bugs/116947
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
*** This bug is a duplicate of bug 141613 ***
https://bugs.launchpad.net/bugs/141613
** This bug has been marked a duplicate of bug 141613
npviewer.bin crashed with SIGSEGV
--
npviewer.bin crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/189701
You received this bug
*** This bug is a duplicate of bug 141613 ***
https://bugs.launchpad.net/bugs/141613
** This bug has been marked a duplicate of bug 141613
npviewer.bin crashed with SIGSEGV
--
npviewer.bin crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/189545
You received this bug
The options only apply to the command itself, ensuring any conflicts are
ignored so the install of the i32-libs library completes successfully.
It doesn't affect anything you later install, or affect any preference
for 32-bit or 64-bit. It provides alternative 32-bit libraries that
32-bit programs
This would be a useful update. Debian already publish 2.01. I've taken
the debian package and Ubuntu-ised it for Gutsy and Hardy and it is in
my PPA:
https://launchpad.net/~intuitivenipple/+archive
Please test it out.
** Changed in: mod-wsgi (Ubuntu)
Importance: Undecided => Low
Assignee
With "quiet" still enabled, try adding this boot option:
ec_intr=1
It should force the GPE to use interrupt mode.
Also, a long shot, but try:
acpi_os_name="Windows 2006"
since the Vaios often have Vista-specific functionality in the ACPI
BIOS.
--
[Hardy] ACPI Embedded Controller (EC) stops b
Vladimir, that is great news!
I'm building test kernels for several ACPI related bugs at present so I
can't test it immediately, but if that proves to deal with this issue as
a workaround until we can locate the root-cause, that is better in many
ways than removing "quiet".
I wanted to record her
Vladimir - that doesn't surprise me! I got the "ec_intr" setting from
Greg Kroah-Hartman's Linux Kernel in a Nutshell, kernel parameters.
However, when I searched the source to find out what it does I find it
doesn't exist!
The good news is 2.6.25-rc9 isn't affected so hopefully we can identify
th
I've discovered the cause of the issue. The system contains an i450NX
chipset which has peer PCI buses. To work around buggy BIOS situations
where these weren't discovered a fix-up was added that looks for and
scans them as secondaries of the first root bus.
This causes the later ACPI code to igno
Patch posted to kernel-team mailing list. Hopefully will be incorporated
before Hardy release.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Impor
** Attachment added: "Gutsy i450NX Dell PowerEdge 6300 fix"
http://launchpadlibrarian.net/13285631/ubuntu-gutsy-pci-i450nx-no-secondary-bus-scan-poweredge-6300.diff
--
-server kernel variant fails to boot on PowerEdge 2650 with AACRAID timeouts
https://bugs.launchpad.net/bugs/149071
You rece
** Attachment added: "Hardy i450NX Dell PowerEdge 6300 fix"
http://launchpadlibrarian.net/13285644/ubuntu-hardy-pci-i450nx-no-secondary-bus-scan-poweredge-6300.diff
--
-server kernel variant fails to boot on PowerEdge 2650 with AACRAID timeouts
https://bugs.launchpad.net/bugs/149071
You rece
Re-allocated i450NX cause to bug #214814
** Changed in: linux (Ubuntu)
Importance: High => Undecided
Status: In Progress => New
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: In Progress => Confirmed
** Attachment removed: "Hardy i450NX Dell PowerEdge 6300 fix"
http://l
stream patch for
v2.6.25-rc8 is attached to the bugzilla report.
** Affects: linux
Importance: Unknown
Status: Unknown
** Affects: linux (Ubuntu)
Importance: High
Assignee: TJ (intuitivenipple)
Status: In Progress
--
BUG: soft lockup - CPU#0 stuck for 61s!
https://bugs.la
** Attachment added: "Hardy i450NX Dell PowerEdge 6300 fix"
http://launchpadlibrarian.net/13298574/ubuntu-hardy-pci-i450nx-no-secondary-bus-scan-poweredge-6300.diff
--
BUG: soft lockup - CPU#0 stuck for 61s!
https://bugs.launchpad.net/bugs/214814
You received this bug notification because yo
** Attachment added: "Gutsy i450NX Dell PowerEdge 6300 fix"
http://launchpadlibrarian.net/13298582/ubuntu-gutsy-pci-i450nx-no-secondary-bus-scan-poweredge-6300.diff
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => TJ
I've just spotted this bug report on the kernel-team mailing list thanks
to Leann. I've been running a Vaio vGN-FE41Z since April 2007. I
started with 32-bit builds but moved to x86_64 and have not tried 32-bit
again since.
I've been testing/using Hardy alongside Gutsy all the way through the
dev
dino99, can you please cc yourself in the following kernel bz and test
the patch posted there?
http://bugzilla.kernel.org/show_bug.cgi?id=10466
Thanks.
--
bad motherboard detection with Hardy 2.6.24-15 & 16
https://bugs.launchpad.net/bugs/212834
You received this bug notification because you
This only affects the x86 i386 build. I'm investigating further.
** Summary changed:
- Hardy boots only in recovery mode on VAIO FE41Z
+ i386 Hardy boots only in recovery mode on VAIO FE41Z
--
i386 Hardy boots only in recovery mode on VAIO FE41Z
https://bugs.launchpad.net/bugs/191137
You receiv
This only affects the x86 i386 build. I'm investigating further.
--
i386 Hardy boots only in recovery mode on VAIO FE41Z
https://bugs.launchpad.net/bugs/191137
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
What we expect to see is:
[ 28.070535] ACPI: EC: Look up EC in DSDT
[ 28.077294] ACPI: Interpreter enabled
[ 28.077357] ACPI: (supports S0 S3 S4 S5)
[ 28.077612] ACPI: Using IOAPIC for interrupt routing
[ 28.078065] ACPI: EC: non-query interrupt received, switching to interrupt
mode
[
A simpler fix was provided by Matthew Wilcox on linux-pci mailing list.
It is cleaner and simpler than my DMI-based patches. Matthew's suggested
patch then came to the attention of Zhao Yakui on linux-acpi who
reported a patch is already in the -mm tree that solves a similar report
at buzilla:
"I
For some reason I can no longer reproduce the issue with the 2008-04-10
LiveCD, and I can't figure out why. I've tried removing the battery and
doing a cold start, with and without external power, restarting from
Gutsy session.
Report back if you're still seeing this issue with the most recent
Liv
On external power, I've just installed the 2008-04-10 Hardy i386 LiveCD.
The LiveCD hangs during boot with the messages:
ACPI: EC: acpi_ec_wait timeout, status=32, expect_event=1
ACPI: EC: read timeout, command=128
However, the *installed* system boots fine:
[ 13.169576] ACPI: EC: Look up EC
** Summary changed:
- i386 Hardy boots only in recovery mode on VAIO FE41Z
+ [Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet'
option is enabled
--
[Hardy] ACPI Embedded Controller (EC) stops boot when kernel boot 'quiet'
option is enabled
https://bugs.launchpad.net/bug
slash2314, thank-you!
In all my testing I usually remove "quiet splash" to watch the boot
messages which explains why I was unable to reproduce it. I also found
this does indeed affect x86_64 as well. Because I run development
kernels I never have the "quiet" option enabled - hence my not being
af
701 - 800 of 2922 matches
Mail list logo
