Bug#706219: Control: retitle -1 No reboot when installing Debian v7.0 RC2 Wheezy i386, Sil 3114 + SATA drive.

Package: installation-reports Control: retitle -1 No reboot when installed with Debian v7.0 RC2 Wheezy i386 on Sil 3114 + SATA drive. Subject: No reboot when installed with Debian v7.0 RC2 Wheezy i386 on Sil 3114 + SATA drive. I will use Wheezy 7.0 stable next time, which has since become

Bug#706219: Subject: No boot, Sil 3114 + SATA drive on Debian installer RC1 wheezy v7.0 i386 20130214-11:13

Package: installation-reports Subject: No boot, Sil 3114 + SATA drive on Debian installer RC1 wheezy v7.0 i386 20130214-11:13 My old unresolved archived bug#607301, Dated 16.12.2010, describes this issue using Squeeze di Beta2. This new graphical install, will not Auto Re Boot using a Silicon

Bug#705956: installation-report (NOW FIXED) HPT370 PATA Boots to ONE disk, NO RAID, using V7 Installer RC1 Wheezy i386 20130214-11:13

Package: installation-reports Subject: installation-report (NOW FIXED) HPT370 PATA Boots to ONE disk, NO RAID, using V7 Installer RC1 Wheezy i386 20130214-11:13 More information is in my previous installation-reports on archived; bug#606416 and bug#610627, about my 'False Raid Controller'.

Bug#681909: Subject: Suggestion: Four Weekly-Build, User writeable, User-Feedback-Status fields, for the Debian web site.

Package: www.debian.org Severity: minor Subject: Suggestion: Four Weekly-Build, User writeable, User-Feedback-Status fields, for the Debian web site. Regarding the the Debian page: http://cdimage.debian.org/cdimage/weekly-builds/ (For me, Testing Wheezy i386 ) BENEFITS: This is not a

Bug#681267: Subject: No kernel modules were found. Weekly build 20120709 debian testing wheezy i386.

Package: http://bugs.debian.org/base Version: 20120709-03:47 Debian GNU/Linux testing wheezy i386 DVD Binary-1.iso Weekly Build 20120709-03:47 to be Debian V7.0 eventually. Install Report -- In case of message formating problems, I used gedit 2.22.3 then Composed and sent in

Bug#607301: I think I misunderstood The SiI 3114 User Manual Page 5. HDDs Function Normally When Not in RAID Sets.

Jump to the last 5 paragraphs in this post, at my tag date 21.04.2011 . I believe I have made a mistake with my configuration set up. 13.04.2011. Otherwise: The error symptom persists using grub-pc 1.99~rc1-12 on same pc: AMD K6-2 cpu, Aladdin V chipset system with only one SATA Non raid, hard

Bug#607301: 1.) More 'No Boot' findings and 2.) effected Grub files; Debian web site grub2 1.99~rc1-6 to rc1-12 changelog text, effected by Bug#622224.

Regarding Bug #607301 No Grub Boot, relation to Bug #64 No Grub Changelogs. Subject: no changelogs created. Grub file sets effected are Debian web site grub2 1.99~rc1-6 to rc1-12 . Quick changing daily Grub Release Candidate files are effected by this. To make Grub maintainers aware, and

Bug#607301: Installation-Report: No Boot with Silicon Image SiI 3114 SATA/Raid Controller + single SATA disk drive and GNU/Linux Debian 6.0.0 i386 New install. No raid array used.

Miguel Figueiredo wrote If I understood correctly: Using a Sil 3114 Sata raid controller you are only able to boot sucessfully in rescue mode. My appologies Miguel, I have not made myself clear. My fault. In response to your question Miguel, my short answer is 'no'. I cannot 'rescue - boot'

Bug#607301: Cannot boot from debian-6.0.1a-i386-DVD Binary-1 20110322-15:11 and sid 29.03.2011 and debian-rescue-cdrom Grub 1.99~rc1-6 Symptom: error: hd0 cannot get C/H/S values

To address your kind response to me Miguel; I read all the links you gave me for my 'Silicon Image 3114' SATA/Raid controller chip. I also followed and read the sub links. I shall certainly be on the look out for disk corruptions. I could not see any mention of my 'NO BOOT' symptom in the links.

Bug#606416: installation-report No boot from HighPoint HPT370 controller PATA raid partition on Debian beta1-20101208

Package: installation-reports Severity: Critical (NOW FIXED.) Justification: No boot means no system. No boot even with rescue-disk-pc TITLE: installation-report_No-boot-from-raid-partition-on-beta1 My filename: issue-instalation-report_No-boot-from-raid-partition-on-beta1-20101208.utf

Bug#606416: installation-report ( NOW FIXED.) HPT370 PATA Boots to ONE disk,NO RAID,using sid (unstable) containing grub-pc_1.99~rc1.3_i386.deb

Package: installation-reports ( NOW FIXED.) Using sid (unstable) containing grub-pc_1.99~rc1.3_i386.deb A good boot process now successfully displays the following: HighPoint Technologies,Inc. HPT370 UDMA/ATA100 RAID Controller BIOS v1.11.0402 (c) 1999-2011. Press CtrlH to run BIOS Setting

Bug#607301: No boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, SATA, SiI 3114

Package: installation-reports Severity: critical Justification: Will not boot, so no system, with or without rescue-disk-pc. Now Debian 6.0.0 is out, should I be sending this report to GRUB package directly ? 06.03.2011 Fails to boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, From

Bug#607301: Install then auto reboot. Failing on auto reboot with Wheezy Testing, Unstable and Experimental.

Package: installation-reports Severity: critical Justification: Will not boot, so no system. 20.02.2011. Install then auto reboot. Failing on any Reboot with Wheezy Testing, Unstable and Experimental. Failing to complete auto reboot after upgrading to Debian 6.0.0 stable squeeze, I upgraded to

Bug#607301: Installation-Report: No boot with Silicon Image SiI 3114 SATA Raid controller + single SATA disk drive and GNU/Linux Debian 6.0.0 i386 New install, No raid array used.

Package: installation-reports Date: 07-10.02.2011 I am moving this issue to Debian Forums after this Installation Report. Installing Debian 6.0.0 stable squeeze ( V6.0.0 ) The 'Debian Graphical Installer Saved Debug Logs' at the bottom of this email Using the same machine, with more details way

Bug#610627: Question. Which piece of software is responsible for picking the GNU/Linux Highpoint disk controller driver hpt366 ?

My appologies Julien. Thank you for your feedback. My report could have been a lot easier for all to read. I am learning, and will strive to do better next time. To save your time, there is no need to comment, unless you want to. http://www.debian.org/devel/debian-installer/ Installing with the

Bug#610627: Question: Which piece of software is responsible for picking the Experimental 'Highpoint Raid controller GNU/Linux driver Pata_HP37X' ?

Thank you Miguel Figueiredo for your kind response. To save your time, there is no need to reply, unless you want to. Only hpt366 is available on Debian's kernel. ( Currently Debian Squeeze, to be V6. ) OK, I assume my 'HighPoint HPT370 raid controller 2001' is, or is partially supported, or

Bug#607301: No boot from SiI 3114 + single SATA drive on di RC2 i386 20101209 New install, No raidArray.

25.01.2011 ( di-rc 2, rc-2, Release Candidate 2. ) Installing from 'Debian squeeze-di-rc2 i386 1' onto the same machine with more details above: Motherboard: MS5169 Processor: AMD K-6-2/400400.9Mhz Controller PCI, Silicon Image SiI 3114 sata raid bios version 5.3.14 2006. Using the

Bug#606242: [Continue] button icon stuck in 'Debian squeeze di rc2 i386',on screen: 'Rescue Operations','Execute a shell in Installer environment'.

On 21.01.2011 Example 10: Debian Installer Release Candidate 2. Using: 'Graphical Rescue Mode' of 'Debian squeeze di rc2 i386 Binary 1.' Screen: 'Rescue Operations','Execute a shell in Installer environment'. I selected the [Continue] button icon, The icon greyed out, the task froze. I made my

Bug#610627: Debian-squeeze-di-RC1-i386 installs wrong driver hpt366 ? for Highpoint hpt370 raid controller. Should it be Pata_hpt37x ?

Package: installation-reports For Debian-GNU/Linux-squeeze-di-RC1-i386 . I do not know which piece of software/package is responsible for picking the GNU/Linux Pata_hpt37X driver, for the Highpoint hpt370 raid controller chip. See the link below;

Bug#606242: Reproduces on multiple machines with multiple type mice, on at least two screen button icons; [Go Back] and [Continue].

installation-reports Package: debian-squeeze-di-RC1-i386-binary-1 install, on 13.01.2011. Using: Debian Installer, Graphical Installer, Release Candidate 1. Change of Mouse to: 'Chic' optical 'faerie' Model: 3902 C255, features a PS/2 plug, two button and a scroll wheel. Machine: Motherboard: A

Bug#606242: Replicated on another machine. Wonky install screen 'CONTINUE' button icon. Debian-squeeze-di-Beta2-i386-DVD-1

I am still working on how to succesfully mount usb thumb drive to get a 'di Saved Debug Log' of a machine that fails the debian-squeeze-di-beta2-i386 install. You can willingly have the logs when I achieve. It's just a matter of time and research. --- A New Observation, 23.12.2010. When the

Bug#606242: Issue-report: Debian-squeeze-di-Beta2-i386-DVD-1. USB+PS/2 mouse and wonky install screen 'CONTINUE' button icon.

Bug#606242. I reproduced on debian-squeeze-di-beta2-i386 New install, the Wonky 'Install screen [CONTINUE] button icon', issue. First a quick conjecture. I wonder if a mouse button action is a 'two state' trigger ? 1.) Button pressed, and 2.) button released. Are these actually really

Bug#607301: No boot from Sil 3114 + SATA drive on Debian squeeze di beta2 i386 20101209 New install.

Package: installation-reports (In case of formatting issues; Composed in gedit 2.22.3 brought over in OpenOffice 3.1.0 and emailed with Firefox 3.6.8 ) TITLE: No boot from Sil 3114 + SATA drive on Debian squeeze di beta2 i386 20101209 New install. My filename:

Bug#606416: NEW TITLE: installation-report: No boot from raid 1 partition on debian-squeeze-di-beta2 i386 new install.

Package: installation-reports (In case of formatting issues; Composed in OpenOffice .odt v3.1.0 , emailed with Firefox 3.6.8 ) My new filename: issue-installation-report_No-boot-from-raid-partition-on-beta2-i386-20101209.utf Boot method: DVD install. Image version: Full URL to image

Bug#602421: 'DVD set' scan, debian-squeeze-di-beta1-i386-DVD-2 label missing from install screen.

Reply-to: 602...@bugs.debian.org Package: installation-reports Christian, Sorry my submit was received in a scrambled format. I do not know why. (I might try taking out the Tabs if it reoccurs.)Here is a resend of my original bug#606227 submission, with my original detail for problem analysis and

Bug#606534: Subject: install fail asterisk 1:1.6.2.0~dfsg~beta3-1 Debian unstable. insserv: Service zaptel has to be enabled to start service asterisk

Package: asterisk Version: 1:1.6.2.0~dfsg~beta3-1 and: 1.6.2.0~dfsg~rc1-1 Justification: renders package unusable Severity: grave Tags: patch My patch is included below. *** This was my first time that I tried to submit a bug. I got it wrong. I do not use email a lot either. I have had a

Bug#606416: Installation-report: No boot from raid 1 (raid1) partition on debian-squeeze-di-beta1 new install.

Package: installation-reports TITLE: installation-report: No boot from raid 1 partition on debian-squeeze-di-beta1 new install. My filename: issue-installation-report_No-boot-from-raid-partition-on-beta1-20101208.utf Boot method: DVD install. Image version: Full URL to image downloaded. Only

Bug#606227: 'DVD set' scan, debian-squeeze-di-beta1-i386-DVD-2 label missing from install screen.

Package: installation-reports TITLE: 'DVD set' scan, debian-squeeze-di-beta1-i386-DVD-2 label missing from install screen. My filename: issue-report:-No-label-shown-on-beta1-install-dvd-scan-20101206.utfb Boot method: DVD install.Image version: Full URL to image downloaded. The first two DVD's

Bug#606242: issue-report: USB mouse and wonky install 'continue' button on debian-squeeze-di-beta1-i386 install.

Package: installation-reports TITLE: issue-report: USB mouse and wonky install 'continue' button. My filename: issue-report:USB-mouse-and-rusty-install-continue-button-20101207.utf Package: installation-reports (I could not progress the install far enough to use the i-r package.) Boot method: