Thanks Carlos Reig!
Either I didn't see that last time I visited the Debugging page, or it
has been added recently.
Anyway, the solution in comment #25 worked for me.
So... it looks like something like this needs to get into Ubuntu by
default for this laptop. I have no idea how that would be
I am happy to report that in Ubuntu 13.10, running kernel
3.11.0-15-generic, this issue has gone away, presumably because the
changes in the upstream kernel I had been using for a while got into the
Ubuntu kernel that is currently installed. I had been running an
unsupported kernel for a while and
I was testing some other issues today and tested this one as well.
I am currrently running Ubuntu 13.10 Saucy with kernel 3.11.0-15-generic
I can confirm that this problem still exists:
- The fn F6/F7 hot keys for brightness show the light bulb and slider but have
no effect on screen brightness
I don't see how this bug can be tested using this method. Can someone
please add the bug-stop-nagging tag? I do not think I have permission to
do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately, due to bug #1257817 I am unable to test Ubuntu ISO images, as of
30 days ago anyway, because I cannot boot off a USB stick with an Ubuntu ISO
image on it.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257817
So, please let me know if there is something else you would like
Good idea. I reported the boot issue at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1257817
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214180
Title:
[Toshiba Portege Z935-ST4N03] will
Public bug reported:
Somehow (and I cannot remember what was involved), after purchasing this laptop
[Toshiba Portege Z935-ST4N03]
in June of 2013, I was able to install Ubuntu from a USB drive, and have set up
a dual-boot system with Windows 8 and Ubuntu.
However, in testing of another bug
Back in August 20, I downloaded the daily build and had the same
problem. I think that would have been Saucy (pre-release). If you can
point me to other specific ISO images you'd like me to try, I'd be happy
to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, I downloaded the ISO from http://cdimage.ubuntu.com/daily-
live/current/ labeled
trusty-desktop-amd64.iso 03-Dec-2013 07:49 884M Desktop
image for 64-bit PC (AMD64) computers (standard download)
and used the Startup Disk Creator utility on my desktop machine (which
is running
A few more notes:
a) This USB stick does boot when I use it in my desktop machine. It just
doesn't boot in the Toshiba laptop.
b) I used a digital camera to record a video of the bootup, and was able
to see the error message. I have attached a screen shot from a freeze
frame (wow, that was
Oh, and I just tried it in the other two USB ports on the laptop. Same
result in all 3. (I believe that one of the ports is USB-3 and the other
are USB-2, so I thought it was possible that would make a difference.)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
As I noted back in August, I am unable to boot this laptop from a USB
stick ISO image of Ubuntu. See comment #5. So I cannot easily test with
the new release to see if it will be fixed.
Do you have just a kernel that I can download and test with? I realize
it won't be a perfect test, but it might
Can I ask here (sorry if inappropriate forum!) -- do you think it is
safe to just continue to use the kernel that I downloaded for general
purposes? I see that it was built for Saucy and I'm on Raring, but it
does appear (at first glance anyway) to work. Thoughts?
--
You received this bug
I downloaded the AMD 64 ISO image from http://cdimage.ubuntu.com/daily-
live/current/ and used the Startup Disk Creator utility to make a
bootalbe USB stick. Then I hit F12 on bootup, went into setup, and made
sure the USB stick was first in the bootup order. Then I tried several
times to boot off
Additional information:
While debugging another issue on this same laptop
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214180) I
installed and booted into the latest mainline kernel (labeled
v3.11-rc6-saucy, following instructions on
https://wiki.ubuntu.com/KernelMainlineBuilds
This
lspci output:
$ lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller
(rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family
Public bug reported:
On my Toshiba Portege Z935-ST4N03 laptop, the display hotkeys and
display brightness settings do not work at all.
Symptoms:
1. When I use Fn F6 or Fn F7, I get a pop-up window that shows a light bulb and
a slider, and the slider goes obediently up and down as I press F6/7.
I am now following the steps on
https://wiki.ubuntu.com/Kernel/Debugging/Backlight
The first step was to reboot with default Linux parameters. I had been
using acpi-backlight=vendor. When I took that out and rebooted, the
symptoms changed: the hotkeys no longer make the slider on the pop-up
2. grep -r . /proc/acpi acpi
** Attachment added: acpi
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778479/+files/acpi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
4. acpixtract acpidump.txt
This produces 4 files, which I'll attach... I guess you have to do each
one as a separate comment.
** Attachment added: DSDT.dat
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778481/+files/DSDT.dat
--
You received this bug notification
** Attachment added: SSDT1.dat
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778482/+files/SSDT1.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214148
Title:
** Attachment added: SSDT4.dat
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778498/+files/SSDT4.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214148
Title:
5. iasl -d DSDT.dat
** Attachment added: DSDT.dsl
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778509/+files/DSDT.dsl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: SSDT3.dat
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778497/+files/SSDT3.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214148
Title:
3. sudo acpidump -o acpidump.txt
** Attachment added: acpidump.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778480/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: SSDT2.dat
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778491/+files/SSDT2.dat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214148
Title:
9. sudo dmidecode dmidecode.log
** Attachment added: dmidecode.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778519/+files/dmidecode.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
7. sudo fwts method fwts_method
Again, the fwts_method file has pretty much anything in it. You might
want to update the instructions so that they say to clear out the
results.log file and attach this instead of redirecting output to
fwts/fwts_method for these two commands.
** Attachment added:
8. dmesg | grep 'ACPI: Video' video
** Attachment added: video
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778518/+files/video
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
10. cat /proc/version version
Linux version 3.8.0-27-generic (buildd@roseapple) (gcc version 4.7.3
(Ubuntu/Linaro 4.7.3-1ubuntu1) ) #40-Ubuntu SMP Tue Jul 9 00:17:05 UTC
2013
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
6. sudo fwts fwts
Note: the fwts file has pretty much nothing in it. I'm assuming what's
wanted here is results.log.
** Attachment added: results.log
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1214148/+attachment/3778510/+files/results.log
--
You received this bug notification
14. As root, I tried
echo 8 /sys/class/backlight/intel_backlight/brightness
Voila! Finally it is doing something. This made the screen almost too
dim to see.
echo 1000 /sys/class/backlight/intel_backlight/brightness
This made the display usable again.
The next step involves rebooting
11. Rebooted with acpi_backlight=vendor (which had been my usual boot
mode; symptoms noted in orginal report).
12.
$ ls /sys/class/backlight vendorbacklight
This reports:
intel_backlight
toshiba
13. As root:
ls -la /sys/class/backlight/intel_backlight/ lslabacklight
(attached)
**
I have just rebooted with kernel parameter
video.use_bios_initial_backlight=0 and it does not behave differently
from the default boot parameters.
So... I think I've finished following all of the steps in
https://wiki.ubuntu.com/Kernel/Debugging/Backlight
- I don't have a Thinkpad.
- I checked
Public bug reported:
After suspending my Toshiba Portege Z935-ST4N03 laptop once and
resuming, I am unable to suspend the second time. When I attempt a
second suspend, the suspend does not complete.
I have tried to suspend via right-clicking on the Power Manager applet, and I
also tried (as
I would just like to add that I followed the instructions on
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume
in the section Suspending from text mode.
Meaning that I booted with no_console_suspend, went into VT1, and did
sudo pm-suspend. The laptop suspended and resumed with no
I got the message today xfhelp4 is not installed when clicking on the
Help button for the Mail Watcher xfce task bar plugin app, for a newly-
installed copy of Xubuntu, after adding the Mail Watcher to my task bar.
Then I tried apt-get install xfce4-utils. However, this didn't work. The
response
I decided to report the Mail Watcher issue to XFCE after all:
https://bugzilla.xfce.org/show_bug.cgi?id=10185
** Bug watch added: Xfce Bugzilla #10185
https://bugzilla.xfce.org/show_bug.cgi?id=10185
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
When I go to the regular Ubuntu download page
http://www.ubuntu.com/download/desktop
it tells me that I need to get the 64-bit download if I am using UEFI firmware,
and suggests 64-bit for newer machines. This is good information.
However, when I go to the Xubuntu download
@davewalker: Thanks for posting your workaround in #9 and clarification
in #14.
I started getting this message in my cron log emails after upgrading from 11.04
to 11.10 last week. The error was coming from the /etc/cron.d/php5 job. You can
also see it in a terminal by running:
% php5
(that's
@davewalker: Thanks for posting your workaround in #9 and clarification
in #14.
I started getting this message in my cron log emails after upgrading from 11.04
to 11.10 last week. The error was coming from the /etc/cron.d/php5 job. You can
also see it in a terminal by running:
% php5
(that's
Thanks, that is very good to know. If I still have this problem when I
upgrade to Jaunty (any day now), I'll try your solution. I've just been
living without sleep.
Incidentally, and I didn't apparently mention it above, with one of the
later kernel updates in Intrepid or something else I or
One more correlary.
There doesn't seem to be a hibernate option from the Gnome menu system
any more.
When I tried the /etc/acpi/hibernate.sh script from a terminal window
within Gnome, the machine did not hibernate to the point of turning off.
It partially turned off: the Gnome display went
I did some more playing around with this today. I'm now running the
2.6.27-11-generic kernel, and I have also tried 2.6.28 and 2.6.29-rc5
(the latter two compiled from kernel.org source). They all behave
similarly, but the testing reported here was with the 2.6.27-11-generic
kernel from Ubuntu.
Just a note: Today I built a 2.6.28 kernel from the kernel.org source,
and I'm still having the same sleep problems reported here.
--
Intrepid regression: Suspend from Gnome menu fails to resume on Twinhead H12Y
clone laptop
https://bugs.launchpad.net/bugs/305339
You received this bug
I tried the command in the previous comment
dbus-send --system --print-reply --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
The result was the same as running from the Gnome menu: failure to
resume (as described
Public bug reported:
Binary package hint: acpi-support
I have an Everex StepNote 2053 T laptop (see below **) that doesn't
resume after a suspend in Ubuntu 8.10 Intrepid; worked fine in Hardy.
More details: I recently updated from Hardy to Intrepid, using the
Update functionality of the
** Attachment added: Output of uname -a and lspci -vnvn
http://launchpadlibrarian.net/20218591/uname.log
--
Intrepid regression: Suspend fails to resume on Twinhead H12Y clone laptop
https://bugs.launchpad.net/bugs/305339
You received this bug notification because you are a member of Ubuntu
** Attachment added: dmesg output (before suspend)
http://launchpadlibrarian.net/20218597/dmesg.log
--
Intrepid regression: Suspend fails to resume on Twinhead H12Y clone laptop
https://bugs.launchpad.net/bugs/305339
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, this is interesting. I was playing around with some of the debugging
suggestions on this page
http://ubuntuforums.org/showthread.php?p=3066404
I found that after a reboot (to make sure I had reset the system to its normal
state), If I went to a terminal window and typed
sudo
Changed package to gnome-power-manager because the sleep.sh script
works, but the Suspend command from System / Shutdown in Gnome menus
doesn't work.
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: acpi-support = gnome-power-manager
** Summary changed:
- Intrepid regression:
If you follow the instructions and get the latest Ubuntu installed,
everything works except the SDHCI card reader (currently -- even that
may shortly be fixed). So you will have a full X-Windows GUI, all kinds
of software, etc.
Here are instructions on how to install, using the Alternate install
*** This bug is a duplicate of bug 198218 ***
https://bugs.launchpad.net/bugs/198218
That's because it's on bug #223061 at
http://launchpadlibrarian.net/14054406/dbug.txt
--
Sound playback doesn't work after suspend/restart in Hardy
https://bugs.launchpad.net/bugs/228020
You received this
Yeah, I've tried volume, mute keys, etc. Nothing helps except the force-
reload described two comments above.
--
Sound playback doesn't work after suspend/restart in Hardy
https://bugs.launchpad.net/bugs/228020
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Someone just changed this bug's status to Fix Released. Could you
point me to the fix so I could test it? So far, there hasn't been a
solution that has worked on
http://bugzilla.kernel.org/show_bug.cgi?id=9905 , and that is the only
place it is being worked on that I'm aware of.
--
sdhci module
The link from the previous comment is from a support thread about a
Thinkpad laptop. I have an Everex laptop, not a Thinkpad, but I did try
their suggestions. The relevant items:
a) use
/etc/init.d/alsa-utils restart
This didn't work on my laptop.
b) Mute the pcm volume and after that the
Doug - That reset command was aimed at people who had sound at startup,
but it went away after a suspend/wake cycle, which is really a separate
bug.
However, your bug is more serious, and actually corresponds to this bug
report. To help the Ubuntu folks check into it, you might want to attach
the
On Bug #223061, someone asked me to try /etc/init.d/alsa-utils reset --
but thsi had no effect on my problem. Here's what I did:
1. Reboot
2. Play the ubuntu Sax.ogg example file (which came with Ubuntu) to verify
that sound is working.
3. Suspend using the Gnome desktop menu item.
4. Restart by
This command has no effect on my problem. Here's what I did:
1. Reboot
2. Play the ubuntu Sax.ogg example file (which came with Ubuntu) to verify
that sound is working.
3. Suspend using the Gnome desktop menu item.
4. Restart by hitting the space bar.
5. Try to play the sound again -- no sound
sudo pulseaudio --check
gives me no output either
--
Sound playback doesn't work after suspend/restart in Hardy
https://bugs.launchpad.net/bugs/228020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, here is what I've found:
* After a reboot, there is a /usr/bin/pulseaudio process running under my user
name. It is apparently not running as a daemon, because my configuration had
daemonize = no in it (as reported by pulseauido --dump-conf).
* After suspend/restart, this process is still
There is some more debugging in Bug #228020 that you might want to check
out.
--
upgraded to hardy heron from gutsy and now sound card does not work, no sound
is being emmited
https://bugs.launchpad.net/bugs/223061
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
I recently upgraded from Gutsy 7.10 to Hardy 8.04 on my Everex StepNote
SA2053T laptop -- see
https://wiki.ubuntu.com/LaptopTestingTeam/EverexStepNoteSA2053T for full
specs, lspci, etc. The audio line from lspci:
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7
Just a quick comment. I found that sound works for me after a reboot,
but stops working after a suspend/restart cycle in Hardy. I filed a
separate bug report on that subject. Sorry if I confused the issue here
by thinking I had completely non-working sound! (The other one is Bug
#228020)
--
The bug is gone in Hardy, so it is probably OK to close. But if you are
still supporting Gutsy, you could try installing phpmyadmin version
described above, then see what the update manager says. Until I upgraded
to Hardy last week, it was still saying this. Anyway, I don't personally
care since I
Jarlath - Which page gives troubleshooting hints? Your message doesn't
list a page. I would be glad to troubleshoot. I am going to start with
https://help.ubuntu.com/community/SoundTroubleshooting
Anyway, I have the same problem on my laptop, and it looks like I have
the same sound card as this
OK, I found the aadebug script. I am attaching the output.
** Attachment added: output of the standard aadebug script
http://launchpadlibrarian.net/14054406/dbug.txt
--
upgraded to hardy heron from gutsy and now sound card does not work, no sound
is being emmited
I just tried the Hardy beta disk, downloaded yesterday.
I think the 8139too problem is resolved. However, the disk still doesn't
boot as a live CD on these laptops, because of the SDHCI module (see
numerous comments above). But I am pretty sure that 8139too got loaded
successfully first. Not
I got an email message from someone who managed to get a standard Ubuntu
distro to install, without a wired network card. He put his experience
in the Ubuntu forums:
http://ubuntuforums.org/showthread.php?t=704260
Note that this person completely blacklisted the SDHCI module, so he has
no wired
An update package that works off the Hardy Alpha already being installed
is not going to help. Those of us with these laptops have not been able
to install off standard Ubuntu distro disks, due to this bug and Bug
#187671, which prevent those disks from even being booted. And even with
this bug
I'm certain the next Hardy Alpha distro disk won't boot, even with this
bug fixed (due to Bug #187671, SDHCI module, as mentioned above) -- but
I have the SDHCI module blacklisted on my laptop, so I could at least
try booting the new kernel, without the rest of the disk, to verify that
the 8139too
Is that config change just for Ubuntu kernels?
Anyway, thanks -- that will get owners of these laptops one step closer
to being able to boot off the live CD and use standard Ubuntu upgrades
for the kernel. (There's still the SDHCI problem, but that's now a
separate bug.)
--
Regression: RealTek
It's likely that this bug also affects the following laptops:
* Averatec 2460
* Everex Stepnote SA2050
* Everex Stepnote SA2050T
* Everex StepNote SA2052T
* Everex StepNote SA2053T
* Philips Freevents x52
* Philips Freevents x53
* Philips Freevents x54
* Philips Freevents x55
* Philips
Public bug reported:
Binary package hint: linux-source-2.6.22
On an Everex StepNote 2053T laptop, loading the sdhci module causes the
machine to hang completely. SysRq keys don't work, and the only way to
reboot is to hold the power switch down.
This is a major problem, because the install disk
Done! The sdhci bug is Bug #187671
--
Regression: RealTek 8139 hard-locks system on installation/modprobe (affects
Averatec, Philips laptops)
https://bugs.launchpad.net/bugs/90271
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I have already tested this problem on the 2.6.24 kernel.org kernel. Do
you think Hardy Alpha 4 is worth testing on -- are there changes beyond
what were in the kernel.org source for 2.6.24 (released last week)?
I did try to test this on Hardy Alpha 3, by the way, but it didn't boot
past the
We reported this, and the 8139too problem, to the kernel folks, via the
kernel mailing list back when I first got the laptop. There has not
been even a reply to that submission. It was months ago, back when
2.6.20 was still current.
We were under the impression that most of the kernel people
I don't agree that Bug #34902 is a duplicate. It is talking about
locking of the system due to a totally different card and driver. The
card/driver on this bug is an 8139 ethernet card (wired network, not
wireless); the card in question for the other bug is a Ralink RT2500
wireless card.
It is
The kernel.org folks released 2.6.24 today (or at least recently). So, I
did some testing with this kernel on my Everex StepNote SA2053T (not an
Averatec - that was a typo in the previous comment I left earlier
today). Results:
1) The sdhci problem still occurs (modprobe -r sdhci causes the
I had the same result as Mike just reported on my Averatek StepNote
SA2053T with the Hardy Heron alpha 3 desktop live CD: boot hangs and the
only recourse is a hard reboot (power switch). The last lines look just
slightly different from the last 2 lines of what Mike reported: the 8139
module is
Public bug reported:
I recently upgraded to Gutsy. After this upgrade, when I run the Update
Manager, I get a greyed-out box for the phpmyadmin package.
So I tried it manually with apt-get install phpmyadmin. It says
phpmyadmin is not installable due to an unmet dependency -- it says it
needs
Public bug reported:
I have an Everex StepNote SA2053T laptop. It will not boot with any
2.6.20 through 2.6.23 kernels (technically I have not tested 2.6.21).
When the boot hangs, it is really stuck, and you can't even use SysRq
keys.
This is not actually an Ubuntu-specific problem but a kernel
Update: After switching from the i810 x-windows video driver with
915resolution, to the intel driver, the brightness keys now work. The
f3/f5 keys have no effect, but at least they do not kill the computer.
--
Display hotkeys not working in Everex StepNote SA2053T
I should note that I did load the 915resolution package, if that is
important.
--
Display hotkeys not working in Everex StepNote SA2053T
https://bugs.launchpad.net/bugs/128572
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: hotkey-setup
The 4 display-related function keys in the Everex StepNote SA2053T do
not work properly. You can press them once, and they will momentarily
blank the screen, which then comes back. But after a second time
pressing any one of the keys (i.e.
85 matches
Mail list logo
