Gutsy ships with these DVB firmware images:
$ ls -l /lib/firmware/`uname -r`/dvb-usb-*
-rw-r--r-- 1 root root 10757 2005-12-01 21:10
/lib/firmware/2.6.22-10-generic/dvb-usb-avertv-a800-02.fw
-rw-r--r-- 1 root root 9180 2005-12-01 21:10
/lib/firmware/2.6.22-10-generic/dvb-usb-dibusb-5.0.0.11.fw
Set to 'Wishlist and allocated to 'linux-restricted-modules'. Assigned
to the kernel-team but please reassign if that is inappropriate.
From my research it appears that although the kernel source-code refers
to this firmware image the site that hosted it,
http://www.thadathil.net/dvb/fw/ (pointed
I'm actively working on this and other hda-snd-intel issues for 2.6.22
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
--
Intel HDA No sound after Standby
https://bugs.launchpad.net/bugs/78257
You received this bug notification because you are a member of Ubuntu
I don't wish to infer that there is no software problem at the root of
this, but I did wonder (because you seem to be seeing this on all kernel
versions), after doing some research on this model if you've tried
inspecting/cleaning/removing/repositioning the keyboard?
I found some references to
Stefano, if the card is handled by pccard services can you try various
commands from pcccardctl, such as:
$ pccardctl status
You can get a list of all available commands using:
$ pccardctl
--
PCMCIA serial card fails to initialise correctly
https://bugs.launchpad.net/bugs/80969
You received
Confirmed fixed with Gutsy Tribe-5 64-bit.
--
[gutsy] 0.10.14-1ubuntu3 regresses multi-cap playback
https://bugs.launchpad.net/bugs/136264
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Using Gutsy Tribe-5 64-bit I appeared to be suffering this problem, but
found an explanation and solution.
1. Open Volume Control
2. Edit Preferences: select all tracks (including Digital so you can keep an
eye on things)
3. On the Switches tab, select Microphone
4. On the Capture tab, ensure
Okay, good news.
One or other update has enabled the headphone functionality correctly,
and I've solved the microphone issue. See my specific comment to bug
#134125:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/134125/comments/6
--
[Gutsy] Tribe-5 64-bit LiveCD failure
Ian, yes it does seem a bit pedantic although to be fair there was a
devils-advocate stance :)
I can see both arguments: On the one hand read-only should mean just
that, it should have the same effect as read-only media. On the other
hand a journalled file-system does need to replay the log to
A couple of observations:
1) On my Sony Vaios at least, they plan for the keyboard to be removed
for access and cleaning. 3-5 screws on the base are removed with a
Jeweller's screwdriver and then the keyboard lifts up at the back. The
clip holding the flat plastic cable into the connector on the
In researching this I've come across a lot of mention of flickering
issues with various Radeon 9x00 chipsets, on Windows as well as Linux.
The symptoms seem to suggest that the framebuffer sets a register
incorrectly.
There are a whole host of settings that can be set on the kernel boot
Looking at hald/util.c I can see at least a couple of places that might
be responsible for this. Back in 2005 there was a patch to fix these
reports called hal-fix-seqfault_if_addon_missing.diff. Unfortunately
hald's util.c has been reworked since then and the issues that patch
addressed may have
I have 4 MA401's here so I'll try them with Gutsy Tribe-5 64-bit and
Feisty 32-bit.
--
Feisty's Kernel Panics With Netgear MA401 PCMCIA Wireless Installed
https://bugs.launchpad.net/bugs/95817
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Indeed. That was the point of my comments. The kernel source-code
contains a reference to a firmware image (dvb-usb-wt220u-zl0353-01.fw)
*not hosted at http://www.linuxtv.org/downloads/firmware/ but was,
according to a Google search, hosted at
http://www.thadathil.net/dvb/fw/.
The DVB-USB
Thanks for that Steve, it helps narrow down the options quite a bit. The
good news is the problem can be reproduced using the scripts so it isn't
just a Gnome issue - this makes it easier to debug.
Secondly, The log shows the PC is told to turn off but refuses so that
takes us into the realms of
So far I've tested all 4 MA401s with Gutsy Tribe-5 64-bit and not had
and problems. I've captured the kern.log events for:
1. Insertion/Removal
2. Boot
I'll attach one log to this comment - if you would like me to do boot-
tests with all 4 please let me know.
I'll do the same tests with Feisty
I should have reported the lspci, lspcmcia and pccardctl responses:
$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT
Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT
Express PCI Express Root Port
Here's the info for the same card from Feisty 32-bit.
$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and
945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT
Express PCI Express Root Port
Can you reproduce this issue after restarting Gnome/restarting the PC?
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) = TJ
Status: New = Incomplete
--
can't undo fullscreen command (F12)
https://bugs.launchpad.net/bugs/137186
You received this bug notification because you
For anyone confused as to which package to install to solve this:
$ sudo apt-get install gstreamer0.10-plugins-ugly
--
[gutsy] 0.10.14-1ubuntu3 regresses multi-cap playback
https://bugs.launchpad.net/bugs/136264
You received this bug notification because you are a member of Ubuntu
Bugs, which
Not an issue with Kino, but with the OS device permissions
** Changed in: kino (Ubuntu)
Status: New = Invalid
--
Kino: libraw1394 - plugdev does not work in Gutsy
https://bugs.launchpad.net/bugs/133862
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has always been an issue for IEEE 1394 AV/C DV devices on Ubuntu
since Edgy at least. The issue is that the user must have read/write
permissions to /dev/raw1394 and the defaults have been changed to
accommodate disk devices:
$ ls -l /dev/raw1394
crw-rw 1 root disk 171, 0 2007-09-06
: apache2 (Ubuntu)
Importance: Undecided
Assignee: TJ
Status: Confirmed
--
Unexplained random HTTP connection failures in hardware load-balanced
web-server farms
https://bugs.launchpad.net/bugs/134274
You received this bug notification because you are a member of Ubuntu
Bugs
Fixed via work-around described
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) = TJ
Status: New = Confirmed
--
Unexplained random HTTP connection failures in hardware load-balanced
web-server farms
https://bugs.launchpad.net/bugs/134274
You received this bug notification
Pending feed-back from the Linux netdev mailing list as to whether this
can be considered a bug in the kernel's implementation of
TCP_DEFER_ACCEPT on this basis:
An RFC standard TCP handshake requires three stages:
client SYN server LISTENING
client SYN ACK server SYN_RECEIVED
client ACK
Assigning to correct package
** Changed in: grub (Ubuntu)
Sourcepackagename: None = grub
--
update leaves bootloader unable to find root partition
https://bugs.launchpad.net/bugs/108554
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I've found that often this is caused when a disk has multiple
partitions, with 2 or more root partitions to support multiple
distributions or versions.
For example, on a new laptop that comes pre-installed with Microsoft
Windows Vista (UUIDs shortened for clarity):
sda1 = UUID=1 Recovery (7GB)
This is almost, but not quite, a duplicate of bug #62195
--
update leaves bootloader unable to find root partition
https://bugs.launchpad.net/bugs/108554
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Gutsy Tribe-5 ( 23 August 2007) 2.6.22-10-generic
Suspend S3/Resume works fine.
--
Network cards not detected when resuming from suspend / hibernate
https://bugs.launchpad.net/bugs/40125
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
Fixed as of Gutsy Tribe-5 2.6.22-10-generic.
--
[Gutsy] LiveCD hangs at shpchp hardware driver
https://bugs.launchpad.net/bugs/121578
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Fixed as of Tribe-5
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Fix Released
--
[Gutsy] LiveCD hangs at shpchp hardware driver
https://bugs.launchpad.net/bugs/121578
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Fixed as of Gutsy Tribe-5 2.6.22-10-generic, with CPU Frequency Scaling
Monitor 2.19.1
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Fixed as of Gutsy Tribe-5 2.6.22-10.generic.
--
Resume failure: Feisty + Sony Vaio VGN-FE41Z
https://bugs.launchpad.net/bugs/116553
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Confirmed on Gutsy Tribe-5 32-bit, Intel ICH7 snd_hda_intel
** Attachment added: udev log
http://launchpadlibrarian.net/8981974/udev
--
No Sound on Login Screen or during Login in Gutsy Tribe 3
https://bugs.launchpad.net/bugs/129029
You received this bug notification because you are a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Intel HDA busted following resume from suspend (No sound after computer exits
standby)
https://bugs.launchpad.net/bugs/78257
You received this bug notification because you are a member of Ubuntu
Bugs,
Same symptoms on Gutsy Tribe-5 32-bit with Intel ICH7. No indications as
to whether the cause is the same.
On Gutsy Tribe-5 after resume the PCI config registers are incorrectly
set-up so the hardware is in AC'97 mode, not HDA. Although the register
affected here is HDCTRL (0x40) this has
** Summary changed:
- Intel HDA busted following resume from suspend (No sound after computer exits
standby)
+ Intel HDA No sound after Standby
--
Intel HDA No sound after Standby
https://bugs.launchpad.net/bugs/78257
You received this bug notification because you are a member of Ubuntu
Bugs,
Confirmed in Gutsy Tribe-5 32-bit. This affects a clean install, not
just the upgrade.
System Preferences menu contains Desktop Effects which when used
causes an Error dialog-box that reads:
Could not launch menu item
Failed to execute child process 'desktop-effects' (No such file or
Confirmed on Gutsy Tribe-5 32-bit.
--
gnome-at-properties - 'Accessible Login' button broken
https://bugs.launchpad.net/bugs/125722
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
the
changes to be written to gnome-2.soundlist. Changes to other options are
written to gtk-events-2.soundlist in the same directory.
Unfortunately this doesn't help to make the user log-in sounds play. I
am continuing to investigate.
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = TJ
Public bug reported:
Gutsy Tribe-5 32-bit.
Attempting to build Gutsy source package gnome-libs-1.4.2 with gcc 4.1.3
(installed with build-essentials):
colors.c:303: error: static declaration of 'my_x_query_colors' follows
non-static declaration
XmHTMLI.h:1063: error: previous declaration of
Public bug reported:
Gutsy Tribe-5 32-bit.
Attempting to build Gutsy source package gnome-libs-1.4.2 with gcc 4.1.3
(installed with build-essentials):
./.libs/libgtkxmhtml.so: undefined reference to `XpmCreateXpmImageFromBuffer'
./.libs/libgtkxmhtml.so: undefined reference to `XpmFreeXpmInfo'
** Summary changed:
- restart does not work in Tribe 5
+ [gutsy] Gnome restart does not work in Tribe-5
--
[gutsy] Gnome restart does not work in Tribe-5
https://bugs.launchpad.net/bugs/134809
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Confirmed with Gutsy Tribe-5 32-bit.
After pressing Ctrl+Alt+Backspace the desktop clears to just the
background image. Occasional hard-disk activity (judging by LED
flashes), Caps-Lock, Scroll-Lock, Num-Lock don't respond - LEDs don't
toggle, cannot switch to virtual console using Ctl+Alt+F1
** Changed in: gnome-libs (Ubuntu)
Status: New = Fix Committed
--
[gutsy] undefined reference to `XpmCreateXpmImageFromBuffer' (and others)
https://bugs.launchpad.net/bugs/134812
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
The system-wide sound settings *should* be read from
/etc/sound/events/gnome-2.soundlist, but Gutsy Tribe-5 isn't accessing
that file.
With an inotify watch on the file in a virtual terminal prior to log-in:
$ inotifywait -m /etc/sound/events/gnome-2.soundlist
no access to the file is reported.
Not a udev issue
** Changed in: udev (Ubuntu)
Status: Confirmed = Invalid
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) = TJ
Status: New = Confirmed
** Changed in: udev (Ubuntu
This issue is caused by wholesale changes to gnome-session between
Feisty (gnome-session-2.18) and Gutsy (gnome-session-2.19.90) in gnome-
session/gsm-sound.c
It appears to be a side-effect of the removal of the dependency on
esound/ESD.
--
[Gutsy Tribe-5] No Sound on Login Screen or during
** Changed in: gnome-session (Ubuntu)
Assignee: TJ = Ubuntu Desktop
** Bug watch added: GNOME Bug Tracker #470348
http://bugzilla.gnome.org/show_bug.cgi?id=470348
** Also affects: gnome-session via
http://bugzilla.gnome.org/show_bug.cgi?id=470348
Importance: Unknown
Status
I'm hoping the desktop team will give this a high priority, because
although it is only an aural cosmetic touch, I think the Ubuntu brand
recognition is very much tied to the distinctive login sounds.
Unless The Gnome developers upstream deal with it quickly, there are 2
options:
1) revert to
I've used the temporary work-around of removing the Gutsy gnome-session
2.19.90 and installing the Feisty 2.18.0 version.
In my previous comment I mistyped the version - it should of course have
been 2.18.0, not 2.1.18!
1. Download the Feisty gnome-session v2.18.0 package
2. Uninstall the Gutsy
I neglected to mention in the previous comment about how to use gnome-
session v2.18.0 that it will cause some functionality to be lost; such
as access to the Suspend Hibernate options and some of the new
Accessibility / Assistive Technology functionality.
--
[Gutsy Tribe-5] No Sound on Login
** Summary changed:
- show desktop plugin enabled, after windows return from scale unalbe to move
windows
+ show desktop plugin enabled, after windows return from scale unable to move
windows
--
show desktop plugin enabled, after windows return from scale unable to move
windows
This may be related to issues with the Nvidia driver. I've been told and
read that Nvidia v100.14.11 in particular has a problem that has been
seen mostly with Compiz if indirect-rendering is enabled. The solution
to that issue is to remove --indirect-rendering from the compiz startup
command.
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
[gutsy] Gnome restart does not work in Tribe-5
https://bugs.launchpad.net/bugs/134809
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
It looks as if this could be a side-effect of the compiz --indirect-
rendering work-around in Amaranth's launchpad Compiz repository. I
chatted with him and the reliance on --indirect-rendering is due to be
removed in the coming weeks, so I think it is a case of wait-and-see but
keep an eye on it,
The suggested kernel patch pointed to by kurt
(http://lkml.org/lkml/2007/5/8/510) was added to the mainline kernel in
2.6.22.2 and is in Gutsy.
Therefore if this issue is still occurring on Gutsy Tribe-5 we need to
look more closely. Please attach the DSDT of the system using:
$ sudo apt-get
Updated upstream bug report since our #470348 has been marked as a
duplicate of this one. Note upstream has this bug marked
Unconfirmed/Minor.
** Changed in: gnome-session
Bugwatch: GNOME Bug Tracker #470348 = 'Bug tracker at
http://bugs.distributed.net/' #466458
Status: New =
** Summary changed:
- Resume immediately after Suspend due to ACPI PM Timer event
+ Resume immediately after Suspend due to some WAKE event
** Description changed:
- When suspending the PC resumes immediately.
+ When suspending (S3) the PC resumes immediately.
- Using a custom-built
** Attachment added: side-by-side diff (SRX41P, SRX51P) of suspend/resume
http://launchpadlibrarian.net/8732203/suspend.diff.txt
--
Resume immediately after Suspend due to some WAKE event
https://bugs.launchpad.net/bugs/128315
You received this bug notification because you are a member of
** Attachment added: side-by-side diff (SRX41P, SRX51P) of dmesg
http://launchpadlibrarian.net/8732204/dmesg.diff.txt
--
Resume immediately after Suspend due to some WAKE event
https://bugs.launchpad.net/bugs/128315
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: linux-source-2.6.22
Gutsy Tribe 1 32-bit LiveCD boot on Sony Vaio VGN-FE41Z.
Always hangs whilst Loading hardware drivers at:
[96.836000] shpchp: Standard Hot Plug PCI Controller Driver version 0.4
Restart required.
This laptop has Intel ICH7
The laptop runs Feisty 32-bit as the default OS. I've attached a
bz2-compressed log of pspci -vvnn. Note that this output was capturing
whilst the PC was running an ACPI debug-build of the standard Feisty
kernel. If you see errors relating to the ipw3945 device it's because I
haven't built the
Feisty 32-bit, 2.6.20-16-generic with ipw3945 and e100 on a Sony Vaio
VGN-FE41Z.
Using just the ipw3945 wireless connection on a WPA2 network.
After resume from suspend NetworkManager reported no network devices.
Restarting NetworkManager didn't seem to solve it.
The solution was to use
*
$ sudo depmod -a
$ sudo modprobe snd-hda-intel
** Affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Assignee: TJ
Status: Fix Released
--
snd-hda-intel missing after uninstalling Linuxant softModem driver
https://bugs.launchpad.net/bugs/124794
You received this bug
Updated to reflect status of report
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = TJ
Status: New = Fix Released
--
snd-hda-intel missing after uninstalling Linuxant softModem driver
https://bugs.launchpad.net/bugs/124794
You received this bug notification
I'm not sure if this report needs re-opening or a new one creating.
Using CPU Frequency Scaling Monitor 2.18.0 on Feisty 32-bit with Intel
Core 2 Duo T7200, when I have 2 panel applets active (one for each core)
if a change is made to one core it is applied to both.
Although this seems sensible
Public bug reported:
Binary package hint: gnome-applets
Feisty 32-bit 2.6.20-16-generic on Sony Vaio VGN-FE41Z with Intel Core 2
Duo T7200.
Using CPU Frequency Scaling Monitor 2.18.0.
With 2 instances of the panel applet active (one for each core), after a
suspend/resume cycle the applet
I'm hearing the same problem on a Sony Vaio VGN-FE41Z.
I read where you say Unloading/reloading the snd-hda-intel module makes
the soundcard work again correctly. I've been unable to do that because
the module is always in-use although I don't know by what:
$ sudo modprobe -r snd-hda-intel
Re: unloading the module. It was in-use even after I stopped GDM and was
working from a console.
I've been debugging this issue and have made a little progress, albeit
not the kind we want.
The difference in the outputs reported here and in bug #55071 pre- and
post-suspend of codex#0 is not of
I decided to track the interrupt/DMA enabling/disabling. I'll put my
notes here in case others want to investigate.
I analysed the sequence of operations in hda_intel.c::azx_suspend(),
azx_resume() and the device initialisation functions.
I noticed that azx_suspend() calls snd_hda_suspend() then
Oh cool! Someone else that knows how to hack :)
I've been reading the Intel HDA Programmers Reference Manual
(http://www.intel.com/design/chipsets/hdaudio.htm) and from what I've
learned so far the problem appears to be with the handling of the output
buffers. Here's the description of what
Funny how you can arrive at the same point from different directions. I
noticed in your tracing that int_cnt had far more interrupts (for the
same file) just after resume than when the module had been freshly
loaded (389 vs 11) and had traced through to the posbuf from struct
azx_dev:
hda_intel.c:1392:
azx_init_stream() {
...
azx_dev-posbuf = (u32 __iomem *)(chip-posbuf.area + i * 8);
--
snd-hda-intel: distorted sound after resume, until the module is reloaded
https://bugs.launchpad.net/bugs/100114
You received this bug notification because you are a member of Ubuntu
azx_setup_controller() is called azx_pcm_prepare():
snd_printdd(azx_pcm_prepare: bufsize=0x%x, fragsize=0x%x,
format=0x%x\n,
azx_dev-bufsize, azx_dev-fragsize, azx_dev-format_val);
azx_setup_periods(azx_dev);
azx_setup_controller(chip, azx_dev);
Now,
Reading this extract from the HDA PRM in conjunction with
azx_setup_controller() (note my ***...*** highlights) might suggest a
problem with ...the hardware may still have pre-fetched descriptors
that will not be flushed when the stream is restarted...:
4.6.6
After the RUN bit has been set, the
Thanks for that report, it was just what I needed. I was already
tracking the various code responsible for updating posbuf and your trace
has confirmed some of what I was expecting. There are several reasons
why posbuf/pos won't be updated so we should try eliminating
possibilities.
In
Yes, I agree. I found some time yesterday to build the alsa-core and
snd-hda modules myself and have been watching the updating of the
hw_ptr_interrupt. I've attached the log. Also, the line
pos -= pos % runtime-min_align;
is, if you read it carefully, not intended to update pos but simply to
I'm afraid I'm seeing no difference here. I had previously checked TCSEL
because of the comment in the head of azx_init_chip(), and I had also
made sure that azx_resume() was called, and in-turn was calling
azx_init_chip().
I also put a check of the value of TCSEL in azx_init_chip() to see what
Sorry - I pasted the wrong line from 'config'!
I see what you mean about TCSEL being reset to 07 when a sound is
played, and when I do 'hexedt config' and change 0x44 to 0, the sound is
corrected - nice one.
So the question is, is there another chip reset operation between
azx_resume() and
OK, it seems we have identified the reason for this problem.
Willem and I worked together on tracing the value of TCSEL after resume.
The code that finally pinpointed the issue was a kernel timer started in
azx_resume() and stopped in azx_pcm_open() with a jiffie interval of 10,
which appears to
What we should have made clear in the two comments above is that we
found by monitoring the PCI config space when the ALSA drivers weren't
loaded that the TCSEL value was still being changed to 0x07 from 0x0.
That was when we decided to implement a timer to find out when the value
was changing.
Is it significant that upon resume the 2nd CPU is resumed *after* PCI
config has been written back to the device and it has been reinitialised
by its driver? When cold-starting the CPU has been started before the
PCI device is configured.
See the attached log-file that compares the relevant
Changed status to Fix Committed now cause is known and patch is
available.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Confirmed = Fix Committed
--
snd-hda-intel: distorted sound after resume, until the module is reloaded
https://bugs.launchpad.net/bugs/100114
You received this
I've tested the latest Gutsy kernel from git (2.6.22-8.18) and found it
doesn't suffer from this bug. In that, the 2nd CPU is started before the
PCI devices are resumed. After resume the HDA device PCI config shows
the TCSEL register is 0x00.
Therefore I'm attaching a patch against Feisty's
Public bug reported:
Binary package hint: linux-source-2.6.20
I have been attempting to boot Feisty 32-bit LiveCD on Dell PowerEdge
6300/550 with 4 Xeon CPUs and several SCSI controllers including a PERC-
II RAID-5 array, and Adaptec controllers for Tape drive and CD-ROM.
Boot from CD fails
** Changed in: casper (Ubuntu)
Sourcepackagename: linux-source-2.6.20 = casper
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: casper = linux-source-2.6.20
** Description changed:
Binary package hint: linux-source-2.6.20
I have been attempting to boot Feisty 32-bit LiveCD
Ridiculous response! The report states that it isn't possible to boot
Linux in order to have access to the tools required to run those
reports!
And, as it is explicitly the 'Feisty 32.bit LiveCD' it's pretty obvious
it equates to 2.6.20-15 generic. Xeon CPUs should give a clue as to the
I'm seeing a similar result with Tribe-2 when choosing to do a Manual
Partition on the 30GB PATA IDE drive in a Sony Vaio SRX51 notebook.
Starting from an empty hard disk with no partition table, boot Gutsy
32-bit from LiveCD and choose to Install. When reaching the Partitioner
choose the
After configuring the partitions using fdisk I restarted Ubiquity, went
to the Partition Manual stage, and tried to simply assign the mount
points to the existing partitions. It allowed me to set partition #1 to
/boot, but after making the changes for #2 to be / it hung up and needed
killing.
--
I've tried various ways to get around this problem, from trying to
assign the mount-points last-to-first (#4, #3, #2, #1) to doing one,
then backing out to the previous step in Ubiquity, and then advancing
again (trying to do one change at a time) but I've so far found no
solution.
Can I
I've discovered some error-reporting from Ubiquity in user.log:
ubiquity[8942]: Ubiquity 1.5.4
ubiquity[8942]: log-output -t ubiquity laptop-detect
ubiquity[8942]: switched to page stepWelcome
ubiquity[8942]: Step_before = stepWelcome
ubiquity[8942]: debconffilter_done: ConsoleSetup (current:
To compare, I've gone through the same procedure with **Feisty** 32-bit
LiveCD and it works so maybe the problem can be found by comparing the
diffs of the two code-bases.
--
while installing gutsy partition manager fails( i386 )
https://bugs.launchpad.net/bugs/123364
You received this bug
In respect of:
* sound is garbled/loops strangely
I posted a patch to fix this in another bug report:
snd-hda-intel: distorted sound after resume, until the module is
reloaded
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.20/+bug/100114
--
Intel HDA busted following resume
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Confirmed
--
while installing gutsy partition manager fails( i386 )
https://bugs.launchpad.net/bugs/123364
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I captured all the logs from this issue and am investigating in as much
as it is possible. I've attached the log tarball to this comment for
anyone else who wants to take a look.
** Attachment added: Tarball containing all Live environment log files
*** This bug is a duplicate of bug 126964 ***
https://bugs.launchpad.net/bugs/126964
** This bug has been marked a duplicate of bug 126964
gutsy livefs causes random hangs or modprobe crashes
--
Desktop hangs on Gutsy Tribe 3 amd64 Live CD
https://bugs.launchpad.net/bugs/127070
You
Looks okay to me Phillip.
I did four boots with it and each one loaded the Gnome desktop
correctly. There were various errors reported during start-up with udev
and acpi (from scripts) but I suspect they're the result of other
issues. One time Gnome reported HAL failed at start but I suspect that
Nice work-around Willem!
I've enhanced your script to make it more modular. Users can install
this script and not have to check and set the PCI device ID as the
script will figure it out.
#!/bin/bash
# this file is /etc/acpi/resume.d/66-snd-hda-intel.sh
# workaround for HDA resume bug on 2.6.20
Martin.
Which kernel version are you using (output from uname -a) ?
I am currently debugging what may be the same issue on a Sony Vaio where
it resumes immediately after suspend. I have a specially built debug
kernel, linux-image-2.6.20-16-generic package (30MB), that reports the
wake-up event
601 - 700 of 2963 matches
Mail list logo
