[Bug 21493] Toshiba M70-181 shows HD LED on constantly

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=21493
Ubuntu | linux





------- Additional Comments From w1 at schulte-ac.de  2005-12-31 14:34 UTC -------
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 ? 
 
 
 
 

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.