Comment 9 for bug 107976
Revision history for this message
| Valerio F. Laube (vflaube-gmail) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I found other people with similar problems:
https:/
http://
( have an workaround )
This weekend I've trieed again to boot Ubuntu Feisty. The results:
1) My first installation was on the partition /dev/hda8 (logical partition), and on this weekend i've tried on /dev/hda1 (primary partition) with GRUB loaded on the MBR.
- Results: the same errors as registered above. (https:/
2) Second attempt: I've installed again in /dev/hda1, but GRUB was entirely loaded in the boot sector of /dev/hda1 (hd0,0). In MBR was installed an boot selector (XOSL). I would test the workaround described in http://
- Results: My computer booted with Feisty Fawn. I've seen some error messages, the boot process was too long, but finally i could see Feisty running on my computer.
I don't undestand why they have booted. i don't have made the workaround from the Ubuntu forum. The only fifferent thing was GRUB entirely loaded in boot sector.
All the partitions of my 2 disks was corrected and named hda (some people report that Feisty names all partitions with "sda")
The sound is ok. Video with resolution 1280x1280. I've changed to 1024x768 and then the image occupied only part of the screen. Then i've runned "dpkg-reconfigure xserver-xorg" and choosed SIS drive. Now the video is also ok.
I hope that Ubuntu developers pay some attention for these problems (bugs?) with SIS chipset. At the moment I can't trust the system (firs successful boot after 10 days, long boot time and and some error messages -> my nest job).
I hope the information above can help others, despite my bad english. Please excuse me for that.