Toshiba M70-181 shows HD LED on constantly

[Werner Schulte]

On my new Toshiba M70-181 Laptop using Ubuntu 5.10, the HD LED is constantly ON.
HD is /dev/sda (SATA). Kernel is "2.6.12-10-686 #1 Thu Dec 22 11:55:07"

I tried to use iostat -dk 2 /dev/sda and found out, that HD is NOT accessed
all the time (puh ;-)). Nevertheless, there seems to be something wrong regarding
the LED`s usage.

The LED is switched on during "loading modules" message and switched of short before
"shutdown" switches off the laptop.

[Ben Collins (ben-collins)]

If possible, please upgrade to Dapper's 2.6.15-9 kernel. If you do not want to
upgrade to Dapper, then you can also try the Dapper Flight 2 CD's:
http://cdimage.ubuntulinux.org/releases/dapper/flight-2/

Let me know if this bug still exists with this kernel.

[Werner Schulte (w1)]

Where to find that kernel (sources) ?
"Dapper's 2.6.15-9 kernel"

[Ben Collins (ben-collins)]

(In reply to comment #2)
> Where to find that kernel (sources) ?
> "Dapper's 2.6.15-9 kernel"

You don't want the source, you want the linux-image .deb, and it can be found by
upgrading to dapper.

[Werner Schulte (w1)]

updated package and all dependendent packages using "synaptic", manual adding dapper source
temporarily to /etc/apt/sources.list.

Here is the result ================

Kernel starts, but graphics shows vertical lines only, boot does not finish.

Starting with vga=791 shows the following output.

insmod: error inserting '/lib/modules/2.6.15-9-686/kernel/drivers/video/console/bitblit.ko' : -1
Unknown symbol in module
insmod: error inserting '/lib/modules/2.6.15-9-686/kernel/drivers/video/console/fbcon.ko' : -1
Unknown symbol in module
insmod: can't read '/lib/modules/2.6.15-9-686/kernel/drivers/video/softcursor.ko
' : No such file or directory
Usage : /bin/sleep seconds
ALERT! /dev/sda2 dows not exist. Dropping to a shell!
and some more lines.

At least the HD LED is off, when showing the above mentioned message. And I saw the Ubuntu
start splash saying "Loading Modules" and switching the LED shortly ON for approx. 1 sec.

=================================

Lets see, whether the old kernel starts ...
Yes, puh ;-))

Note : I am working productively with that laptop.

So whats about building that kernel from source ?
Sometimes thats few destructive. Is the source-package
for 2.6.15-9 available as well (preconfigured ?).

P.S.
Forgive me if I ask silly questions, but this installation is my first time using Ubuntu. Before
that I used Debian Sarge and before that Suse (until 8.2). So even, if I am impressed about
the tremendous work you guys did for Ubuntu, I need that laptop for work - and thus a stable
environment.

[Ben Collins (ben-collins)]

(In reply to comment #4)
> insmod: error inserting
'/lib/modules/2.6.15-9-686/kernel/drivers/video/console/bitblit.ko' : -1
> Unknown symbol in module
> insmod: error inserting
'/lib/modules/2.6.15-9-686/kernel/drivers/video/console/fbcon.ko' : -1
> Unknown symbol in module
> insmod: can't read '/lib/modules/2.6.15-9-686/kernel/drivers/video/softcursor.ko
> ' : No such file or directory

Your initrd image is not updated. Run this command:

sudo update-initramfs -u

Then reboot.

[Werner Schulte (w1)]

Same problem ...

sudo update-initramfs -u

running the 2.6.12-10 kernel

did not complain. File initrd-2.6.15-9-686 was at least touched.

Error messages are the same, than before.

[Ben Collins (ben-collins)]

(In reply to comment #6)
> Same problem ...
>
> sudo update-initramfs -u
>
> running the 2.6.12-10 kernel

Then you aren't completely up-to-date with dapper. That error is from using
pre-dapper udev with a dapper kernel. You need to update /etc/apt/sources.list,
and do an "apt-get dist-upgrade", and then rerun update-initramfs. This means
you wont be able to rerun breezy kernel very well (since new udev, and lack of
hotplug is not compatible with the old kernel).

[Werner Schulte (w1)]

I think thats dangerous, and I would not like to do so.
I mentioned already to have a productive system on that laptop,
which needs to be as stable as possible.

[Ben Collins (ben-collins)]

(In reply to comment #8)
> I think thats dangerous, and I would not like to do so.
> I mentioned already to have a productive system on that laptop,
> which needs to be as stable as possible.

If it were dangerous, I would not be asking it of you.

If you choose not to assist with debugging this, that's your choice, but let me
remind you that without any debugging help, this will likely not be fixed for
dapper, which means you'll have to deal with this bug indefinitely.

[Werner Schulte (w1)]

Created an attachment (id=5525)
Firefox screenshot of dapper.

[Werner Schulte (w1)]

Ok, gave it a try ...
Repartitioned my disk and installed a Breezy server to get the result as quick as possible.
Installation went smoothly, updated to the latest breezy packages, edited /etc/apt/sources.list
to dapper and did an "apt-get update;apt-get dist-upgrade".

That ended with a cupsys-driver-gimpprint problem which could NOT be resolved and did not
let me install other packages.

Another try ...
Installation of breezy desktop went smoothly, updated to the latest breezy packages,
edited /etc/apt/sources.list to dapper and did an "apt-get update;apt-get dist-upgrade".

Same problem as above.
Rebooted the system and was at least able to install new packages (always with the cupsys error
message at the end).

Both dist-upgrades did NOT install a 2.6.15-8 kernel. Also the try to update the linux-686
package surprised me. Installed version 2.6.15-8 : last version 2.6.15-8, but not vmlinuz
and /lib/modules package found. Also the try to update linux-image-686 (which shows 2.6.12.16.1
installed and 2.6.15.8 as new, but no 2.6.12.16 available on my machine) did not succeed. Package
depends on 2.6.15.10, but thats not available.

P.S.
- Still have the firefox problem (see attachment)
- network did not come up. Had to start manually.

P.P.S
Thats what I mean unstable.
I surely want to help to get linux stuff stable, but I also need a chance to that on a minimum
risk and time (took me the complete day to find out, that it doesnt work).

P.P.P.S
Where can I get a defconfig file for the 2.6.15 kernel sources to try that ones ?

[trollord (trollenlord)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.