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 available. ISSUE: I used the same hardware and configuration I detailed earlier in this report. GNU,Linux,Debian seemed to successfully install until the reboot. POST (Power On Self Test) at reboot after installing, shows an error:- No valid device ! Press any key to continue MODULES/DRIVERS: I know Drivers and BIOS have to match up together. Is this the case with the GNU,Linux,Debian module/driver sata-sil version 2.4 ? I was wondering which Silicon Image supplied BIOS should be flashed into the Sil3114 controller to work with the Debian sata_sil v2.4 driver/module, currently supplied in Wheezy Release Candidate 2 ? Is this my issue ? I installed using Debian v7.0 RC2 Wheezy i386 20130420-14:50 using the Graphical Installer, and have Sil 3114 SATARaid BIOS Version 5.3.14 displayed during the POST of the Motherboard AMIBIOS when connected to a single SATA drive, which is the only drive in the machine. Looking at an FAQ listing at www.siliconimage.com/support/ sil3114 PCI to 4 port SATA 150 controller; Under the heading: Which Driver and or BIOS should I use ? ( of course for Microsoft) It says; When selecting a driver for upgrade or installation, pick the latest released driver for your Silicon Image controller part number. Install the driver that is the same type as the BIOS you have installed for your controller. I have currently controller BIOS SATARaid (FakeRaid) but want the function for controller BIOS IDE/nonRAID for use with Linux MDADM software raid. ENVIRONMENT: PARTITION DISKS: Guided Partitioning, Use the entire disk, Select the entire disk, Select the disk to partition, Partitioning Scheme: All files in one partition. I resized /swap from 466.6Mb to 2.0GB and / from 159.6GB to 158GB, This is an overview of your currently configured partitions. SCSI2 (0,0,0) -160.0 GB ATA ST3160815AS #1 primary 158.0GB BF ext4 / #2 primary2.0GBF swap swap # /bin/lsmod (Just the interesting modules/drivers.) ata-generic, pata_ali, sata_sil, scsi_mod, libata, mii, 3c59x. # /bin/list-devices disk /dev/sda (OK, correct, I have one hard disk installed.) LOGS: # bin/nano /var/log/syslog (Just the interesting lines follow.) kernel: linux version 3.2.0-4-486 (gcc version 4.6.3 (debian 4.6.3-15) #1 debian 3.2.41-2 kernel: legacy DMI 2.0 present. kernel: DMI: system manufacturer system name/ALADDIN5, BIOS 0626 kernel: WARNING: at/build/buildd-linux_3.2.41-2-i386-BfAj4s/linux-3.2.41/arch/x86/pci/irg.c:206 pirg_ali_get +0x23/0x43() kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) kernel: SCSI subsytem initialised kernel: libata version 3.00 loaded. kernel: sata_sil :00:0e.0: version 2.4 kernel: PCI: setting IRQ 9 as level-triggered kernel: sata_sil :00:0e.0: found PCI INT - IRQ 9 kernel: sata_sil :00:0e.0: Applying R_ERR on DMA activate FIS errata fix kernel: scsi0 : sata_sil kernel: scsi1 : sata_sil kernel: scsi2 : sata_sil kernel: scsi3 : sata_sil kernel: ata1:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec80 irg 9 kernel: ata2:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec00 irg 9 kernel: ata3:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec80 irg 9 kernel: ata4:SATA max UDMA/100 mmio m1024@0xebfeec00 tf 0xebfeec00 irg 9 kernel: scsi4 : pata_ali kernel: scsi5 : pata_ali kernel: ata5: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq14 kernel: ata6: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq15 kernel: ata5.01: ATAPI: PIONEER DVD-RW DVR-110, 1.41, max UDMA/66 kernel: ata5.01: WARNING: ATAPI DMA disabled for reliability issues. It can be enabled kernel: ata5.01: WARNING: via pata_ali.atapi_dma modparm or corresponding sysfs node. kernel: ata5.01: configured for PIO4 kernel: ata1: SATA link down (SStatus 0 SControl 310) kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) kernel: ata2.00: ATA-7: ST3160815AS, 3.AAC, max UDMA/133 kernel: ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) kernel: ata2.00: configured for UDMA/100 kernel: scsi 1:0:0:0: Direct-Access ATA ST3160815AS 3.AA PQ:0 ANSI:5 kernel: ata3: SATA link down (SStatus 0 SControl 310) kernel: ata4: SATA link down (SStatus 0 SControl 310) kernel: scsi 4:0:1:0: CD-ROM PIONEER DVD-RW DVR-110 1.41 PQ:0 ANSI:5 kernel: sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB) kernel: sd 1:0:0:0: [sda] Write Protect is off kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 kernel: sd 1:0:0:0: [sda] Write cache: enabled, Read cache: enabled, doesn't support DPO or FUA kernel: sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray kernel: cdrom: Uniform CD-ROM driver Revision: 3.20 kernel: sr 4:0:1:0: Attached scsi
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 Image, Inc PCI SATA RAID controller 2006 and a SATA disk, after installing Debian GNU/Linux installer RC1 wheezy v7.0 i386 20130214-11:13. I am after the fast disk control bus and future proofing, by buying SATA DASD (Direct Access Storage Devices) and not pata. I will not be using the FakeRAID for any hardware raid supplied by the Sil3114. See DRIVER CONFIGURATION: at the end of this report. I wanted, and eventually intend to use, the Linux Debian MDADM Software raid 1, if and when I can get the Debian WHEEZY install working. I bought a few of these 2006 controller cards to upgrade my machines from Dabs.com a couple of years ago. Base System Installation Checklist: [O] = OK. [E] = Error Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives:[O] Partition hard drives: [O] Install base system:[O] Configure Package Manager: Scanning DVD set disk, Binary-1,2,3. Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader: [O] Overall install: [E] Will not auto boot into new installed system, at end of install process. BOOT METHOD:Before installation; Booting the DVD to install with 'Debian Graphical Installer'. After installation; to boot from the only DASD (Direct Access Storage Device = Hard Disk Drive) MBR (Master Boot Record) in the machine, not including the unpopulated DVD-ROM. Alas, this reboot fails. Image version: The three dvd binaries of Debian GNU/Linux installer RC1 wheezy v7.0 i386 20130214-11:13 Configure Package Manager: Scanned DVD disks set Binary-1,2,3. Machine:Motherboard: MS5169, Verion 2.1, AL9. Processor: AMD K-6-2/400 400.9Mhz Memory: Memtest86+ v4.10 224MBpass:1, errors:0 Chipset:ALI M1541, + ALI M1543. Bios: American Megatrend AMIBIOS 1996 A5169MS v2.6 121598 51-1215-00-0011-071595-41E_43C-MS5169-T99-H PCI to SATA controller board: Manufacturer: For Best Ports Connection Sil 3114 sata raid bios version 5.3.14 2006. Serial ATA host controller card SA3114-41R 4 port. chip: Silicon Image Inc, StealVine Sil 3114 CTU. printed on the chip: QG6332.1-10644AD03AX2. printed on the sata pci board: SATA3114-A01 FG-SA3114-4IR-01-BC01 or it might be: FG.SA3114.4IR.01.BC01 Jumper 4, two pin, is for the disk activity LED. According to the box it came in: and its manual SA3114-41R Compliant with serial 1.0 specification up to 1.5 Gb/s Raid 0 and 1. Supports co-exist RAID set and Non-RAID HDD. Remember, I am after Non-RAID HDD support for the fast disk control bus and future proofing, by buying sata dasd and not pata. I do not intend to use the FakeRAID, or any hardware raid function supplied by the Sil3114 for software MDAM RAID1. DASD: The only hard disk drive in the machine: Seagate, Barracuda 7200.10, 160GB, SATA up to 3.0 Gb/s Model: ST3160815AS, p/n: 9cy 132-304 Firmware: 3.AAC, Date code: 07422, Site code: TK, Thailand. Jumper:A jumper is supplied for 1.5 Gb/s. Currently both unjumpered = up to 3.0 Gb/s. (will auto select speed to 1.5 Gb/s.) Partition Disks SCSI 1 (0,0,0,) (sda) - 160 GB 1.0 MB FREE SPACE # 1 2.8 GB F swap/swap swap # 2 157.3 GBB F ext4/ / 859.6 kB FREE SPACE I believed swap space should come first (quickest to get to) especially on a small RAM machine. I noticed that the Wheezy Guided Partition puts the swap partition at the end of the list. I want to understand why. Until I investigate, I will follow the imperical 'swap partition last' in list, the next time I install. If it starts swapping, you want swap to be quick to get to. Thrash me if I am wrong. BIOS: AMIBIOS HIFLEX setup utility v1.21 1998 American Megatrends. Standard cmos setup: Screen 1. Fast Boot bypasses filesystem checkup ( currently on.) Base memory: 640KB Extd memory 223 MB 229,376KB Advanced CMOS setup: Screen 2. 1st Boot device: SCSI ( As written in the Sata raid pci Board user manual.) 2nd Boot Device: CD-ROM (There is a reason for this boot order.) 3rd Boot Device: Disabled. 4th Boot Device: Disabled. Try other Boot Devices?: NO. ( I tried yes to above line, and it did not recognised the SATA board.)
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'. BOOTS UP OK, using the RC1 graphical installer DVD and re ipl's itself ok after the install. OK, I get error message Gnome 3 failed to load, but I am pleased the HPT370 HighPoint Raid Controller 2001 supporting code had moved to and since from Sid, and over to Debian GNU/Linux Installer Release Candidate 1 Wheezy 7.0 i386 20130214-11:13 succesfully. Thank you to those involved who achieved this for the first time. See further down for bios settings etc. Initially my intention and I failed:- Boot method: DVD graphical installer setting up for booting, using an array called /dev/md0 built on two hard drive disks, configured for raid1 mirroring mode. I used the latest current downloaded testing dvd image, of the time. Debian official snapshot i386 dvd binary1 20110108-16:28. Yes, January 2011. Only the first DVD 1 of the set was required. I first began using earlier installs of 'testing' then Date: 08 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz. Processor: AMD AThlon K7, 850 Mhz, Socket 'A' Memory:SDRAM 2 x 512Mb = 1Gb. Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. DASD: (Direct Access Storage Device = Hard Disk Device in this case.) Quantity x2, brand new at the time, IBM Deskstar, Manufactured August 2000, Made in Hungary, Model DTLA-307030 ATA/IDE Capacity 30.7 GB Part Number: 07N3929, LBA: 60.036.480 sectors, CHS 16383 / 16 / 63, Using Ultra 100 cables. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level. CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, ( Just try booting the same disk again) Boot other device: disabled. Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled. Two additional IDE channels provide the capability of adding high performance device(s) to system. IDE HDD Block Mode:Enabled. for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid) Is not used by me for 'hardware raid' here now. The intention was and will be to use the HPT370 for Debian GNU/Linux MDADM Software raid1 mode (mirroring) using Debian-GNU/Linux-Squeeze-di-RC1-i386. Yes, Squeeze RC1 was current when I tried this the first time. Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402 HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY STATUS shows no array. Good! I am not using any raid function for this boot, just using the HiPoint controller as an additional, fast, IDE controller. Ultra ATA100. Time goes by; Debian GNU/Linux V7 Wheezy RC1 is now current, Yes Wheezy, AND IT WORKS. I have two: IBM-DTLA-307030 drives, intended eventually as primary master and secondary master connected to the High Point HPT370 controller, The green sockets on my motherboard, attached with Ultra ATA100 ribbon cables that have only two plugs on each cable. the motherboard end and the master device end. Note: no Cable Slave plug. My intention is still to set up O/S software raid at a later date. Off Topic, As an aside, these two drives bought from new, Moo, intermitantly. They always have Moo'ed, just like an animal. A cow in the far distance. As I live in a rural area, I thought for months that an animal was calling. I started to get distressed for this animal and began to sound locate 360 degrees. Having located the origin, this Raid issue allowed me to run one drive at a time for months and identify that both drives moo. I assume its the bearings. It does not seem to effect performance. The DASD work. Back on topic. With only ONE hard drive attached in the machine, and all set up for fault finding. Updated Modular BIOS: V6.00 PG. With Cmos Setup Utility 2002 Award Software: 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level. Standard Cmos Features: IDE Primary master: none. IDE Primary slave: none. IDE Secondary master: LITE-ON LTR-16102B DVD rewriter. IDE Secondary slave:none. Advanced Bios Features: 1st boot device: CDROM. 2nd boot device: CDROM. 3rd boot device: Was HDD-0. Now set to CDROM Boot Other Device: enabled. Delay for IDE Initial (Secs) 0. Floppy 3 mode support: disabled. Intergrated Peripherals: Onboard IDE-1 Controller: enabled. No Hard Drives are connected here. Onboard IDE-2 Controller: enabled. No Hard Drives are connected here. White coloured sockets on the motherboard for IDE-1 and IDE-2. USB Controller: Was disabled. Now set to enabled. (for printer and mouse.)
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 complaint, it is meant as a well intentioned observation and suggestion, I believe it is a way to speed up the bug/fix cycle with quick feedback and also increasing Debians available resources by involving outside help, us Users. PROPOSITION: It would be helpfull if the the Weekly Build Status page included four, User changeable, User Feedback fields:- A first single field; with two dropdown selectable options for 'User Feedback' flags, referencing the current Weekly Build feedback from USERS, such as; No known issues or Unknown, Uninstallable, or Broken + Uninstalable. (A multiple choice, drop down selection.) A second field for a Bug# number to enable a visiting User to quickly track the status, helping the User make their download decision, quickly and efficiently, instead of taking the best part of a day to find out its broken. A third field, of open text Issue Description field, for text like Weekly Build cut 20120702-03:50 for when there is no 'bug report number' yet, because nobody is working on the issue. This gives an instant indication and opportunity to a user, like me to download, investigate and report the broken Weekly Build as a new bug. These 'User Feedback Status' fields would go a long way to making life easier to decide if its worth downloading, maybe cutting a disk, and going through the install process before finding out the Weekly Build is broken and will not boot. A fourth field that is automatically updated with the date of the User change. --- CURRENT WEB PAGE: http://cdimage.debian.org/cdimage/weekly-builds/ Currently the (URL above) page says: Weekly build status Last updated: 20th October 2011 All running normally, no issues to report. ( I know that it has been broken for for at least 3 to 4 weeks.) Possible bugs affecting the weekly builds No bugs found Last bug check: 2012-07-17 08:10:02 UTC (today is 17.07.2012) I assume this means, ...with the build disk packaging, which is reasonable statement. EXPERIMENT: One proposed suggestion may be to conduct a 6 month experiment by creating and allowing on that page, a public access, User Status Feedback fields and Date field, so that we users could help, by updating the Weekly Build (WB) Feedback Status. Text could be added nearby with a disclaimer and warning that this feedback is user changeable and may be wholly inaccurate. If the experiment is not helpfull, or is abused, just tweak or fine tune fields and text accordingly or stop the experiment. REASON FOR CHANGE: I would not have downloaded for so many weeks, the first two DVD's and cut the first DVD (no net), then spent the time trying to install each time, a known (by someone) broken uninstalable WB (Weekly Build) iso. I could not see from previous bug searching, in advance, unless I had the symptoms to search with from my many own fruitless installs and resulting issues. I am guessing here of course, the Weekly Builds are auto built, which I now suspect they are, I trust that this is already the process. It appears there may be nobody trying to check to see if the Weekly Build actually installs. Maybe this has probably been a glitch, has occured to me, and probably due to the lack of people resources. If I am wrong, then I do appologise. Of course, holding back on publishing, or pulling the build is NOT an option in my view. People need to work on something. That's why my proposed 'WB USER Feedback Status Fields', to 'flag the WB iso' idea of mine, may be of assistance in helping you decide the appropriate measure, if any, to be taken here by (Debian) you. The detail reason for my comments are contained in one of my installation-reports. In this case, regarding Weekly Build 20120702-03:50 I have no bug# number to reference here yet, as I have not submitted the 'Package: instalation-reports:' report yet, (work in progress). HISTORY: Bear in mind that recently, more Wheezy Testing Weekly Builds have install bugs that have not allowed a succesfull install, for various reasons. I did try, but failed to install, using; The Debian-Installer Alpha 1, and Testing Wheezy i386 Weekly Build's; Dated; 20120611-04:04, 20120618-04:03, 20120702-03:50, 20120709-03:47. Maybe, yes maybe due to bugs; #674100, #676302, #638682, 681267 respectively. To finish, I value everbody's work on Debian.org web site and am overawed with, and gratefull to; GNU, Linux and Debian and the App developers. I hope my above comments help, they are meant to. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 plain text with Firefox 3.6.17, and google.mail. iso passed the sha512sum check and the DVD passed the CD-ROM(s)integrity check. Whilst performing a Graphical Install and after the set up for root plus password, and user plus password set up, I received the 'Debian Installer' error message :- First Symptom:- -- Load installer components from CD No kernel modules were found. This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. If you are installing from a mirror, you can work around this problem by choosing to install a different version of Debian. The install will probably fail to work if you continue without kernel modules. Continue the install without loading kernel modules ? ESC button. Debian Installer-Main Menu ( DI-MM ) Execute a shell # cat /var/log/syslog | /bin/more As an aside, is it to much to ask for less to be available on future binary-1 disks ? System Summary:- -- Processor: AMD Athlon, 32 bit, single core, 850 Mhz, Family ID:6, Model ID: 4 Motherboard: www.abit.com.tw 8363-686A (KT7-RAID) Not used in raid mode. Memory: 1024 MiB Chipset: Via Technologies VT8363 Bios:Award Software V6.00 PC Release 07/11/2002 PCI devices: One of which is :- HighPoint Technologies, Inc. HPT370 Is an 'on system board' Faker Raid controller, udma 100 IDE. Only one drive is used on this controller and machine. DASD: A single 30.7 GiB ATA IBM-DTLA-307030 with three partitions. P1. 1.6 GiB ext4 /swap, P2. 29.0 GiB ext4 /, P3. 100 MiB GPT /boot. syslog excerpts:- cdrom-detect: CDROM mount succeeded: device=/dev/sr0 fstype=iso9660 cdrom-detect: Detected CD 'Debian GNU/Linux testing Wheeezy - Official Snapshot i386 DVD Binary-1 20120709-03:47 main-menu: INFO: Menu item 'load-cdrom' selected cdrom-retriever: Warning: unable to find contrib/debian-installer/binary-i386/Packages in /cdrom/dists/wheezy/Release. cdrom-retriever: Warning: unable to find contrib/debian-installer/binary-i386/Packages.gz in /cdrom/dists/wheezy/Release. anna: WARNING **: no packages matching running kernel 3.2.0-2-486 in archive --- # cat /cdrom/dists/wheezy/Release | /bin/more Has inside it... 81 main/debian-installer/binary-i386/Release 168962 main/debian-installer/binary-i386/Packages 45682 main/debian-installer/binary-i386/Packages.gz # ls /cdrom/dists/wheezy/Contrib/binary-i386 and /il8n only. The two cdrom-retriever: Warning: unable to find contrib/debian-installer/binary-i386/Packages in /cdrom/dists/wheezy/Release. seems to be valid. Thanks to everybody involved, for your help with this issue, and for Debian in general. Regards From: techy x's tech x's t...@gmail.com with no spaces or x's. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 disk attached to the SiI 3114 Raid controller. In the bios:- 1st boot device set to SCSI. 2nd Boot device set to CDROM With the cdrom empty. The error symptom persists: SiI 3114 SATARaid BIOS Version 5.3.14 Silicon Image, Inc. Press Ctrl+S or F4 to enter RAID utility 0 ST3160815AS 149GB No valid device! Press any key to continue... or) Press Ctrl+S or F4 to enter RAID utility Searching for Boot Record from SCSI..Not Found Searching for Boot Record from CDROM..Not Found Boot Failure Reboot and Select proper Boot device or insert Boot Media in selected Boot device Press any key when ready --- # less /boot/grub/device.map (hd0) /dev/disk/by-id/ata-ST3160815AS_9...A --- When trying to start the already installed system on /sda1 via the rescue disk in the cdrom drive, using grub-rescue-cdrom 1.99~rc1-12 from grub-rescue-pc 1.99~rc1-12 The rescue cdrom itself successfully boots on the same machine. Editing the rescue disk 'GNU/Linux, boot command list' to experiment only, to help identify where the error messages are coming from. I have no intention to boot the system with this experiment edit. GNU GRUB version 1.99~rc1-12 echo 1 set root=(hd0,1) set root=(hd0,1) echo 2 echo 3 echo 4 linux /vmlinuz root=/dev/sda1 /vmlinuz root=/dev/sda1 echo 5 echo 6 end. Then booting with F10 followed by a quick press of the Pause/Break key on the keyboard to stop the screen output timing out and disappearing, gave: Booting a command list 1 set root=(hd0,1) 2 3 4 Linuz /vmlinuz root=/dev/sda1 error: hd0 cannot get C/H/S values. 5 6 end. Press any key to continue... -- 21.04.2011. It looks like I have made, at least, another mistake. Reviewing my issue yet again, I decided to check out when booting up, the Silicon Image Bios message :- No valid device! Press any key to continue... Yes, the first error message encountered. I know to follow the first error indication. I have been searching on the net and discovered that there are TWO basic types of firmware for the card. 1.) With RAID( SATARaid ) 2.) WithOUT RAID ( SATALink ) Going back and rereading my SATA/Raid card documentation, along with the internet entries I have since found, without realising, I had assumed, there would be no change in firmware. To date, I have not touched the firmware. I have not loaded the non raid firmware when I started using a single sata attached hard disk drive. I thought it would make fault finding easier, by making things less complex, with just one hard disk. I will have to rethink the SATARaid User's Manual page 5. HDDs Function Normally When Not in RAID Sets. copyright 2003 Silicon Image Inc. I thought the No valid device! message meant no valid raid array. I now believe it means; that there is no valid Direct Access Storage Device (DASD), that the BIOS can communicate with. If so, I need to either :- 1.) Install a second disk to make a valid RAID array, or 2.) Change the SiI 3114 to (non raid) SATALink firmware. For what it's worth, grub-rescue-cdrom 1.99~rc1-12 and rc1-13 has the same symptoms. Although this post started life as an Installation Report. It is now what may probably be a user error (mine). So with hindsight, I should not be posting on this mailing list. For politeness and completeness, I will attempt to take this issue to it's conclusion, elsewhere if need be, then update a final posting here. I'm learning. Regards, McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 also to check I am using the correct list. On 11.04.2011 I submitted a notice just for the Grub files effected that I went to look at. a 'BROKEN LINKS notice' for Debian Grub-pc and Grub-rescue-pc to http://lists.debian.org/debian-www/2011/04/msg00086.html I received a response email back highlighting known bug #64. A summary of my submission to debian-www is:- I was hoping to use the following Debian links for: 1.99~rc1-6 to: rc1-12 http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-12/changelog but there is no Debian web site grub2 1.99~rc1-6 to rc1-12 changelog text yet. Changelog link is positioned at the right hand side column called 'Debian Resources'. http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-12/changelog for package pages: http://packages.debian.org/sid/admin/grub-pc and http://packages.debian.org/sid/admin/grub-rescue-pc --- Changing subject back to fault finding bug #607301. Another observation whilst using Debian grub-rescue-cdrom 1.99~rc1-6 to find my /dev/sda1 from the grub-rescue-cdrom command line: grub ls (cd) (cd,msdos1) (fd0) My note: This last ls command takes 3 minutes and 37 seconds to complete on my machine. (cd) (cd,msdos1) (fd0) is displayed instantly, along with the flashing cursor at the end of the same line. the command completion is signified 3 mins, 37 secs later by:- the cursor doing a 'carriage return and line feed' to display: grub -( The flashing cursor appearing on this next line.) I assume that grub is searching unsucessfully for other devices, such as my /sda, then eventually times out. --- For more previous detailed information on Debian bug #607301 at:- http://lists.debian.org/cgi-bin/search?query=607301 I achieved 13 hits when I tried just now. The reason ? Some of my entries have either been reallocated and or closed. In my mind incorrectly, but in good faith. It's not a problem to me. Either way, there is more of my own work details and results in them. --- 07.04.2011 To correct one mistake I made in my earlier posting. While I experimented with grub-rescue-cdrom 1.99~rc1-6 again and editing the default 'GNU/Linux','Booting a command list' to:- echo 0 setparams 'GNU/Linux' echo 1 echo 2 set root=(hd0,1) echo 3 echo linux /vmlinuz root=/dev/sda1 linux /vmlinuz root=/dev/sda1 echo 4 initrd /initrd.img --- booting with F10 followed by a quick press of the Pause/Break key on the keyboard to stop the screen output timing out and disappearing, gave: Booting a command list 0 setparams GNU/Linux 1 2 set root=(hd0,1) 3 linux /vmlinuz root=/dev/sda1 error: hd0 cannot get C/H/S values. 4 5 initrd /initrd.img Press any key to continue... --- So the 'error: hd0 cannot get C/H/S values' message resulted from the stanza ' linuz /vmlinuz root=/dev/sda1 ' probably due to the ' set root=(hd0,1) ' stanza, not working. I am 'best effort' guessing here, I just do not know. This corrects my mistake with my previous post on this observation --- Pressing the Tab key on the keyboard to use the 'command completion' facility while editing the stanza:- set root=( as inset root=([TAB]gives:- Possible devices are: cd fd0 --- Other than keep trying the latest code, does anybody have any ideas what other information I should provide, for me to help progress a resolution to my symptom :- error: hd0 cannot get c/h/s values please ? Again, thanks to all. Regards, McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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' the newly installed pc debian system with, or from, rescue mode, with the aid of the 'rescue cdrom' disk and it's Grub GNU/Linux 'Boot Command List'. The 'rescue cdrom' disk, boots itself in the pc OK ! Having booted the rescue-disk itself, I cannot use the running rescue disk's GNU/Linux 'Command List' to 'rescue - boot' the debian system previously installed on hard disk. McTech wrote at Message #27 received at 607...@bugs.debian.org Subject: No boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, SATA, SiI 3114 Date: 06.03.2011. Fails to boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, The rescue disk boots itself ok, but it does not rescue the machine. The pc does not boot in conjunction with the rescue disk, after succesfully installing from, (except auto booting) versions of :- Debian 6.0.0, wheezy weekly build , unstable-20.02.2011 and also experimemtal-20.02.2011, and experimental-04.03.2011. After I set the rescue-disk-pc GNU/Linux parameters to :- set params 'GNU/Linux' (as it comes, a blank line here) set root=(hd0,1) linux /boot/vmlinux-2.6.37-2-486 root=/dev/sda1 initrd /boot/initrd.img-2.6.37-2-486 The rescue-disk-pc Boot Symptom is :- error: hd0 cannot get c/h/s values error: you need to load the kernel first. press any key to continue grub ls (cd) (cd,msdos1) (fd0) Today, 10.04.2011, I can see Ubuntu's https://launchpad.net/ubuntu/natty/+source/grub2/1.99~rc1-10ubuntu1 I can also see the following Debian link is there at http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-10/changelog but no Debian web site, Grub rc1-10 changelog text yet. http://packages.debian.org/changelogs/pool/main/g/grub2/ no rc1-10 entry yet. I will wait a while. --- Minor corrections to errors I made in my previous 04.04.2011 posting:- Using debian-rescue-cdrom Grub 1.99~rc1-6 should be Using Debian grub-rescue-cdrom 1.99~rc1-6 issue suappears should be issue appears . root@grml / # /dev/sda0(just to see) should be root@grml / # ls /dev/sda0 (just to see) ls: cannot access /dev/sda0 : No such file or directory. Again, thank your help Miguel. It is appreciated. Regards, McTech. I am progressing this potential grub symptom in help-g...@gnu.org I am not sure how I specify specific message or bug numbers, or join / link up the seperate entries there at help-grub. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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. including your pointer which eventually lead to Bug 10480 Summary: sil3114 yields ext3_new_block: Allocating block in system zone I came across: https://ata.wiki.kernel.org/index.php/Sata_sil Known problems Some reports of data corruption when paired with NVIDIA chipsets. McTech; I have an ALADDIN5 chipset. For my clarity, that's a number five. The great item I learned from your tip, was that I should not depend searching so much on http:groups.google.com I do not remember coming across your links in my own searching, so thank you. I suppose I was using different search arguments. I thought I had done such a thorough job. I am indebted to you for expanding my search horizons Miguel. If I get data corruption errors, such as kernel: EXT3-fs error kernel: EXT2-fs error or some such, I will know where to look and what to try. So far, I have had no data corruption errors that I am aware of, but then I have not been explicitly looking for them. I have seen no error messages re data corruption, I do get my:- Searching for Boot Record from SCSI..Not Found Boot Failure and that is after a complete installation, of about, I don't know, 15 or 20 various successfull install data transfers. See my /sbin/e2fsck -nv /dev/sda1 clean output below. Of course, I will be looking out in my install logs in future. cat lspci -nn.txt anddmesg -s 100 Output from lspci -nn lspci -nnvvvxxx I will keep a look out for the symptoms described in the following link :- https://bugzilla.kernel.org/show_bug.cgi?id=10480 Comment #8 From Jan Kara 2008-04-24 They (the error messages) generally mean the filesystem is corrupted. In this particular case, bitmap of used blocks is corrupted as system blocks (most likely inode table) are marked as freed in the bitmap of used blocks and then we tried to allocate from there... Miguel, Using grml-daily-sid 110316 codename grml-live-autobuild [2011-03-16] the following is a disk analysis report from my single disk system :- root@grml / # mount /dev/sda1 ... /dev/sda1 on /mnt/sda1 type ext3 (rw) root@grml / # umount /dev/sda1 root@grml / # /sbin/e2fsck -nv /dev/sda1 e2fsck 1.41.12 (17-May-2010) /dev/sda1 was not cleanly unmounted. check forcedMcTech?? Pass1. Checking inodes, blocks, and sizes Pass2. Checking directory structure Pass3. Checking directory connectivity Pass4. Checking reference counts Pass5. Checking group summary information 113443 inodes used (1.16%) 954non-contiguous files (0.8%) 166non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 7293/60/0 1390543 blocks used (3.57%) 0 bad blocks McTech 1 large file 89420 regular files 9396 directories 12character device files 25block device files 2 fifos 419 links 14578 symbolic links (13474 fast symbolic links) 1 socket 113853 files Currently, this disk and controller seems all right to me. So thank you Miguel. I am not sure if the following is the correct protocol. I shall continue my efforts by sending an email Installation-report with package: grub-rescue-pc-1.99~rc1-6 to help-g...@gnu.org. http://lists.gnu.org/archive/html/help-grub/ http://lists.gnu.org/mailman/listinfo/help-grub , and hopefully temporarily put to sleep this thread, Bug#607301 Debian Package: installation-reports here at; http://lists.debian.org/debian-boot/2011/02/msg00320.html I hope this is the correct procedure. If I am standing on anybody's toes, my appologies in advance. Correct procedural guidance is always welcome here. Mucho gracias Miguel F, Melhores cumprimentos. Thank you for your help and time. Best regards,McTech -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 Package: installation-reports (I could not progress the install this far.) Boot method: DVD install. Image version: Full URL to image downloaded. Only the first DVD 1 of the set is required. Date: 08 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz. Processor: AMD AThlon K7, 850 Mhz, Socket 'A' Memory:SDRAM 2 x 512Mb = 1Gb. Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level. CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, Boot other device: disabled. Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled. Two additional IDE channels provide the capability of adding high performance devie(s) to system. IDE HDD Block Mode: Enabled. for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid) Not used by me for 'hardware raid'. The HPT370 is used by me, only for the fast disk control bus. Linux Debian MDADM Software raid will be used when I can get that far into the 'squeeze-di-Beta1' install. Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402 HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY STATUS shows no array or devices. Good! screen button F1 toggles the view CHANNEL STATUS which shows the devices: DASD: quantity two: IBM-DTLA-307030 drives, primary master and secondary master, Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the HPT370 controller. Good! HPT370 Bios Setting Utility option 7. Set Boot Disk: I have set no disk as Boot Disk here, as I believe the 'Linux Software Raid Array' is the place to specify /dev/md2 /boot as bootable in partition manager, which I have set. IDE Primary master: none. IDE Primary slave: Pioneer DVD-ROM ATAP (I do not use this.) IDE Secondary master: LITE-ON LTR-16102B DVD rewriter (I use this all the time.) IDE Secondary slave:none. Partitions: df -Tl df: invalid option --'T' BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary. usage: df [-Pkmh] [FILESYSTEM]... df -h Filesystem SizeUsedAvailable Use%Mounted on tmpfs 505.4m 92.0k 505.3m 0% /dev /dev/md126.6g 473.6m 24.8g 2% /target /dev/md292.0M 17.5M 69.7M 20% /target/boot /dev/md126.6G 473.6M 24.8G 2% /dev/.static/dev tmpfs 505.4M 92.0K 505.3M 0% /target/dev Output of lspci -nn 00:00.0 Host Bridge [0600] Via Technologies ... (rev 02) 00:01.0 PCI Bridge [0604] ... AGP 07.0 ISA bridge... Appollo Super South ... (rev 22) 07.1 IDE ... PIPC Bus Master IDE ... (rev 10) 07.2 USB Controller [0c03]: Via Technologies VT82x UHCI USB1.1 Controller ... (rev 10) 07.3 USB1.1 Controller ... (rev 10) 07.4 BridgeVT82c686 [Appollo Super ACPI]... (rev 30) 11.0 Ethernet controller ... 00:13.0 Mass storage controller [0180]: HighPoint Technologies, Inc. HPT ... /370/ ... [1103:00041] (rev 03) 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:47421] (rev 5c) Base System Installation Checklist: [O] = OK. [E] = Error Initial boot: [O] Detect network card:[O] Configure network: [N/A] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Configure Package Manager: Scanning DVD set disk, Binary-1 only. (yes) Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Won't auto boot into new installed system. --- /var/log/syslog excerpt 2010 :- Dec 8 11:39:18 kernel: [ 486.432151] md: md2 stopped. Dec 8 11:39:18 kernel: [ 486...] bindhdg1 Dec 8 11:39:18 kernel: [ 486...] bindhde1 Dec 8 11:39:18 kernel: [ 486...] raid1 personality registered for level 1 Dec 8 11:39:18 kernel: [ 486...] raid1: raid set md2 active with 2 out of 2 mirrors Dec 8 11:39:18 kernel: [ 486...
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 Utility Scan Devices. Please wait Primary Master: IBM-DTLA-307030 Primary Slave:No Drive Secondary Master: IBM-DTLA-307030 Secondary Slave: No Drive (Gives all the local peripheral data here.) PCI device listing ... (Gives all the PCI peripheral data here, such as:- ) BusNo 0, DeviceNo 19, FuncNo 0, Vendor 1103, Device 0004, Class 0180, Mass Storage Cntrlr, IRQ 11. Verifying DMI Pool Data Boot from ATAPI CD-ROM Boot from ATAPI CD-ROM GRUB loading. Welcome to GRUB! GNU GRUB version 1.99~rc1-3 Debian GNU/Linux, with Linux 2.6.32-5-686 and with due process, up comes the Debian login. It worked ! After moving to; GRUB version 1.99~rc1-3 on Debian GNU/Linux, with kernel Linux 2.6.32-5-686 with my original RAID array mirror, ( Mode 1, RAID1 RAID-1 ) my MD0 Array, a set of two pata disks, would still not boot. I deleted the array, resinstalled and the machine succesfully booted as above, from one disk hde, NO RAID. This is where I am todate. Next I will get farther up the learning curve regarding setting RAID1 mirrors, booting and do another reinstall again, bringing in hde and hdg next time, to create an mdadm RAID1 md0 array. Well done and a big thank you to whoever, did what. I saw in the GNU/Linux Debian GRUB 1.99~rc1-3 changelog, so many changes. I am not sure what you busy people changed to get my situation booting. I hope this installation-report helps anybody. Thank you, Regards McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 a Sil 3114 controller and a single SATA drive. No raid array is set. grub-rescue-cdrom.iso: El Torito CDROM image. The rescue disk boots itself ok, but it does not rescue the machine. The pc does not boot in conjunction with the rescue disk, after succesfully installing from, (except auto booting) versions of :- Debian 6.0.0, wheezy weekly build , unstable-20.02.2011 and also experimemtal-20.02.2011, and experimental-04.03.2011. After I set the rescue-disk-pc GNU/Linux parameters to :- set params 'GNU/Linux' (as it comes, a blank line here) set root=(hd0,1) linux /boot/vmlinux-2.6.37-2-486root=/dev/sda1 initrd /boot/initrd.img-2.6.37-2-486 As a reminder from way above, this processor is: AMD K-6-2/400, along with all the other machine and system details. The rescue-disk-pc Boot Symptom is :- error: hd0 cannot get c/h/s values error: you need to load the kernel first. press any key to continue grub ls (cd) (cd,msdos1) (fd0) I also tried with the rescue-disk-pc 1.99~rc1-3 set root= (sd0,0) or (sd1,0) or (sd0) or (sd0,1) or (sd1,1) or (sda,1) or (sda) error: no such disk. I set it back to hd0,1 and tried again. No joy. back to the symptom. I can use the 'install disk, graphical rescue mode' to /dev/sda1 ok. # eject /dev/scd0 works, along with other sda1 resident applications. # /usr/bin/nano /etc/apt/sources.list # /boot/grub/grub --version grub (GNU GRUB 1.99~rc1-3) I also ran # /usr/sbin/update-grub2 I tried booting from the dasd without using the rescue-disk-pc to hd0 again, but it would still not boot afterwards, or with a subsequent rescue-disk-pc. In the machines AMIBIOS setup - Advanced CMOS setup :- With the cdrom trays empty, a boot from the DASD with 'SCSI' set in the machines Bios as '1st Boot Device' and further Devices set to disabled, still gives :- Searching for Boot Record from SCSI..Not Found Boot Failure Reboot and Select proper Boot device or insert Boot Media in selected Boot device Press any key when ready With CDROM set as '1st Boot Device' and SCSI set as '2nd Boot Device' still gives:- Searching for Boot Record from CDROM..Not Found Reboot and Select proper Boot device or insert Boot Media in selected Boot device Press any key when ready You would think that with the last (2nd Boot Device) set as SCSI, the 4th from last line would still say :- Searching for Boot Record from SCSI..Not Found. as this would be the last device it tried to boot from. Further boot devices are set to disabled. I hope my installation-report helps with the GRUB Release Candidate 1-3 work. Regards McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 Wheezy Testing weekly build snapshot i386 20110204-05:44 which fails to reboot at the end of the install to single SATA drive from a DVD. # grub-install -V (GRUB) 1.98+20100804-14 (Via rescue mode) I then net-upgraded to unstable Sid 20110218 which also failed to complete the auto reboot at the end of the net upgrade. # grub-install -V (GRUB) 1.99~rc1-3 I then upgraded to Debian experimental 20110220 which also failed to complete the auto reboot at the end of the net upgrade. Experimental at this time has the same grub-pc package version as the Wheezy testing weekly build snapshot i386 20110204-05:44 namely (GRUB) 1.99~rc1-3 All and any reboots from the single drive have the same failure, with symptom: No valid device! Press any key to continue... or) Press Ctrl+s or F4 to enter RAID utility My Note: I believe this is as it should be, as the RAID controller BIOS tells me that there are no RAID arrays set up by me, as I am just using the RAID controller, not for RAID but to drive my single SATA disk drive and the controller's faster bus. Disk Controller: Card Manufacturer = For Best Ports Connection PCI chip: Silicon Image SiI 3114 sata raid, bios version 5.3.14 2006. More machine details are way above here. Reboot Symptom (continued), Motherboard BIOS talking now: Searching for Boot Record from SCSI .. Not Found Boot failure Reboot and Select proper Boot device or Insert Boot Media in selected Boot device Press any key when ready. Note: Just for clarity, I set the mobo BIOS setting to boot, first, from the SCSI, not the CDROM. Using the Wheezy DVD 'Advanced Options','Graphical rescue mode' but being carefull to use the /dev/sda located programme, Debian Experimental 20110220, not the Rescue Wheezy snapshot 20110214. # cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/disk/by-id/ata-ST3160815AS_9R... (Note: My ...) /usr/sbin/grub-install -V grub-install (GRUB) 1.99~rc1-3 # /usr/sbin/grub-install --recheck /dev/sda Installation finished. No error reported. # cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/disk/by-id/ata-ST3160815AS_9R... # /usr/sbin/update-grub2 Generating grub.cfg... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found Linux image: /boot/vmlinuz-2.6.32-5-486 Found initrd image: /boot/initrd-2.6.32-5-486 done # grub-probe -vd /dev/sda grub-probe: info: opening hd0. grub-probe: info: the size of hd0 is 312581808. grub-probe: error: unknown filesystem. /home/CJWatson/src/packages/grub2/grub2.debian/grub-extras/zfs/zfs.c:1984:label 0 # cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/disk/by-id/ata-ST3160815AS_9R... # /usr/sbin/grub-mkdevicemap util/deviceiter.C:376: Already seen /dev/disk/bu-id/SCSI-SATA_ST3160815AS_9R... /dev/sda util/deviceiter.C:376: Already seen /dev/sda util/deviceiter.C:814: No DM devices found # cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/disk/by-id/ata-ST3160815AS_9R... A reboot from the single DASD fails. I hope this installation-report helps. I am certainly learning. Thank you for keeping up the good work. Regards, McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 above :- Motherboard:MS5169 Chipset: ALi Corporation, Aladdin V Bios: American Megatrend AMIBIOS 1996 A5169MS v2.6 Processor: AMD K-6-2/400400.9Mhz Disk Controller: Manufacturer = For Best Ports Connection PCI, Silicon Image SiI 3114 sata raid bios version 5.3.14 2006. lspci -knn Subsystem: Silicon Image, Inc. Device [1095:7114] lspci -knn: Kernel driver in use: sata_sil Using the Debian 6.0.0 Squeeze Graphical Installer i386 February 2011, gives the same symptoms as the di-Beta1, Beta2, RC1 and RC2 installs :- I noticed during the install, 'running update-grub' seemed to take a long time. from the start of the Grub2 install to the Grub2 Install completion, the duration took 1:08 minutes:seconds, of which 0:96 :seconds was 'running update-grub'. Initially, I 'graphical di- installed GRUB2 boot loader to the master boot record ? 'YES', At a later 'graphical di-install, I answered 'NO', for /boot to go in it's own partition. Finish the installation: Installation complete, so it is time to boot into your new system ... [Go Back] 'Save debug logs to floppy' of the graphical install :- of the install that used :- 'Partioning Method:' 'Guided - Use entire disk' 'Partioning scheme','All files in one partition' 'Install GRUB into MBR (Master Boot Record)' Yes, a floppy, I never did manage to achieve mounting a usb thumbdrive (yet). Having installed succesfully so far, to the end of the install, when the install auto reboots through the bios, I get the same fault symptom. The hardware post and bios progress ok. When the bios hands over to continue the boot process from a hard disk. It seems unsuccessful. I get boot screen symptom :- SiI 3114 SATARaid BIOS Version 5.3.14 0 ST3160815AS149GB No valid device! press any key to enter to continue... or press Ctrl+S or F4 to enter RAID utility ( I believe thats normal, as I have no raid array set up. ONE disk drive only.) 'Searching for Boot Record from CDROM... Not found. (A blank line) Boot Failure Reboot and Select proper Boot Device Press any key when ready' *** This is where the install fails. It does not boot up from the disk into the newly installed system. *** As an experiment, I changed the boot sequence in the BIOS; 'American Megatrends AMIBIOS,Setup-Advanced CMOS Setup 1998', by taking out the first entry: CDROM and replacing it with SCSI, setting DISABLED in the 2nd,3rd and 4th boot device field and the remaining boot sequence field 'Try other boot device = NO'. A reboot gives:- 'Searching for Boot Record from SCSI... Not Found. (A blank line) Boot Failure Reboot and Select proper Boot Device Press any key when ready' *** This is where the install fails again. It does not up boot from the disk into the newly installed system. *** === Change of environment: I di-installed GRUB2 to /boot and using Debian 6.0.0 graphical 'Rescue mode','Device to use as root file system:' /dev/sda1 'Rescue operations','Execute a shell in /dev/sda1' # blkid /dev/sda1 : UUID =54a ... SEC_TYPE=ext2 TYPE=ext3 /dev/sda1 : UUID =4d1 ... TYPE=SWAP # cat /boot/grub/device.map (hd0) /dev/disk/by-id/ata-ST3160815AS_9 ... # ls /boot/ grub initrd.img-2.6.32-5-486 vmlinuz-2.6.32-5-486 system.map-2.6.32-5-486 config-2.6.32-5-486 # mount /dev/sda1/ on / type ext3 ... etc ... # /target/bin/date Fri Jan 14 ... UTC 2011 (Wrong date in the saved logs.) should be Feb 10 2011. [Go back] Screen: 'Rescue operations','Re install GRUB Boot Loader'. seems to work ok. Rebooting afterwards without the Debian DVD gives the same fault symptom :- 'Searching for Boot Record from CDROM... Not found. (A blank line) Boot Failure Reboot and Select proper Boot Device Press any key when ready'. === SAVED DEBUG LOGS from dgi (Debian Graphical Installer) i386 HIGHLIGHTS: Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27 Unpacking grub-pc (from .../grub-pc_1.98+20100804-14_i386.deb) ...(Syslog entry) lspci -knn: Subsystem: Silicon Image, Inc. Device [1095:7114] lspci -knn: Kernel driver in use: sata_sil There is no log in /target/var/log/lastlog There is only one log. That in /var/log/syslog. The machine date seems to be at, and the Syslog is prefixed with; Jan 13-14th. It should be 10.02.2011. I will look at the TOD clock, the next time I work on this machine. My appologies. Hardware-summary uname -a: Linux debian 2.6.32-5-486 #1 Fri Dec 10 15:32:53 UTC 2010 i586 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: ALi Corporation M1541 [10b9:1541] (rev 04) lspci -knn: Subsystem: ALi Corporation M1541 [10b9:1541] lspci -knn: Kernel driver in use: agpgart-ali lspci -knn:
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 Debian-Installer After using the Debian-Installer, please send us an installation report, even if there weren't any problems. http://d-i.alioth.debian.org/manual/en.i386/ch05s04.html#submit-bug Debian GNU/Linux Installation Guide. The Debian Installer team 5.4. Troubleshooting the Installation Process 5.4.6. Submitting Installation Reports Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Mctech wrote: My thoughts, comments and ideas had during the install. Package: installation-reports [O] = OK. [E] = Error Overall install: [E] Won't auto boot into new installed system. Comments/Problems: ... 'grub-install /dev/mdo fails (raid-1)' ... is very relevant to my 'Unable to boot from raid1' symptom situation ... The same symptoms since installing Beta1, Beta2 and now Debian-squeeze-di-RC1-i386 Release Candidate 1. (jump to my summary “Finally...” at the end of this entry below and return here.) ... Finally, This report is just for my perceived driver issue... I believe this bug#606035 'grub-install /dev/mdo fails (raid-1)' fix is very relevant to my 'Unable to boot from raid1' symptom situation. My reporting above therefore reflect the symptoms of bug#606035 as well, but not to be addresed here in this installation report by me. This report is just for my perceived driver issue. https://ata.wiki.kernel.org/index.php/Pata_hpt37x 'HighPoint 370 series PCI ATA Controllers'. If we are still waiting for Pata_hpt37x maybe, Q. which driver should the software be choosing to install ? Answer: I now know hp366 should have been and WAS selected in squeeze di RC2. *** There is no sign of module hp37x, for the ( hp370, hpt370, hpt 370, hpt-370 ) *** Q. Is this as it should be ? Answer: Yes. I now know it is in Experimental, although I have not checked yet. or is this the cause of ONE of my fault symptoms ? I do not know. Q. Which piece of software is responsible for picking the GNU/Linux driver hpt366 ? Answer: I do not know, but is currently an irrelevant question. I think my bug report MAY be valid. If not, I appologise in advance if I am wasting people's time. Currently, I do not have the needed experience to take this further AND achieve the Debian imminent release timescales. I am now more enlightened. --- If my next text piece here, is cross posting, then I do understand 'cross posting' is fround upon. I do it to make life easier. It is for readers convenience Julien, here are some brief exerpts from one di installation-report I filed as :- Debian Bug#606416 Package: installation-reports No boot from raid1 partition on debian-squeeze-di-beta1 new install. (For this same machine, more details way above). Machine: Motherboard: 'A bit' KT7, Raid, 1 Ghz, 1Gb SDRAM. Processor: AMD AThlon K7 DASD chip: On-motherboard HPT370 raid controller 2001. www.highpoint-tech.com ( hardware raid) (Fake raid I believe ?) Is not used by me for 'HARDWARE raid '. The intention is to use the HPT370 for Debian GNU/Linux MDADM 'SOFTWARE raid' mode 1 (mirroring) using Debian-GNU/Linux-Squeeze-di-RC2-i386 soon to be Debian V6. Comments/Problems: Using graphical installer: The CD or DVD with the following label has been scanned: Debian GNU/Linux squeeze-di-beta1_Squeeze_-Official Beta i386 DVD Binary-1 20101027-01:46 If you wish to scan another CD or DVD, please insert it now. Scan another CD or DVD? (No) Trying to boot from a raid 1 (mirror) set. I installed the GRUB boot loader to the master boot record. Finish the installation : Installation complete, so it is time to boot into your new system... The hardware post and bios progress ok, but when bios hands over to continue the ipl from a disk, it just waits. *** This is where the install fails. It does not auto boot up into the newly installed system. *** END of excerpts from Debian Bug#606416. Thank you again Julien for your feedback. Regards, McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 not at all, in di-RC2. No need to reply. pata_ modules are marked as experimental and are not compiled so they are not missing. I look forward to the new Debian Testing images. I trust Experimental will mature to Unstable then Testing over the coming months. If not, I MAY trial Experimental Image iso, just to see the result, so no need to reply. http://identi.ca/debian?page=2 2011.02.06 The new testing wheezy starts as a copy of the old testing squeeze and not unstable. As your controller was detected and works i am closing this bug report. I appreciate your time spent and your reply Miguel. From the time I spent here, and searching, I am sure you appreciate, it was not my intention to waste your time. Thank you again Miguel Figueiredo for your response, and everyone involved in producing Open Software.Regards, McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 graphical installer, gives the same symptoms as the Beta-1, Beta-2, RC-1 installs :- Initially, I installed GRUB boot loader to the master boot record ? YES, At a later install, I answered NO, for /boot to go in it's own partition. Finish the installation: Installation complete, so it is time to boot into your new system ... Having installed succesfully so far, when the install auto reboots through the bios, I get the same symptom. The hardware post and bios progress ok. When the bios hands over to continue the boot process from a hard disk. It seems unsuccessful. I get symptom :- Searching for Boot Record from CDROM... Not found. (A blank line) Boot Failure Reboot and Select proper Boot *** This is where the install fails. It does not boot up into the newly installed system. *** Using the Graphical Rescue Mode on: Debian GNU/Linux squeeze- di-rc2_squeeze_-oficial snapshot i386 DVD Binary-1 20110121-14:41 Selecting: 'Installer boot menu','Advanced Options'. At screen: 'Enter rescue mode','Device to use as Root FiLe System:' I selected /dev/sda1 ( It found the 'SiI 3114' sata disk sda1 ) At screen: 'Enter rescue mode','Rescue operations' I selected 'Execute a shell in /dev/sda1 At screen entitled: 'Enter rescue mode',Interactive Shell on /dev/sda1' # mount shows: /dev/sda1 on /target type ext2 (rw, ... /dev/sda3 on /target/boot type ext3 (rw) # mount /boot # /usr/bin/nano /boot/grub/device.map showed (hd0) /dev/disk/by-id/ata-ST3160815AS_ 9 ... I must confess I THINK device.map originally specified (hd0) I will check again, when I re install again. 26.01.2011 GRUB (Legacy) Now changing to a different environment on the same machine. Using Grub Rescue Disk 'Grub-0.95-i486-pc-iso' . Rescue Disk 'Booting command-list' I cannot get grub to recognise my single sata hard disk drive. I thought ' root (sd0,2) ' would have been the correct device. Alas any sd gives: ' Error 23: Error while parsing number '. I believe GRUB doesn't distinguish between ide and scsi (or sata), so the 'hd' nomenclature is correct for all hard drives. A drive number above hd7, such as hd8 gives: Error 12: Invalid device request.( It seems reasonable to me.) I have since tried from hd0,0 through to hd7,7 with no success. Grub 0.95 Symptom: Error 21: Selected disk does not exist . Regards Mctech. Thank you one and all for the Great Software. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 notes, then slightly moved the mouse pointer, still within the confines of the icon frame. The task unfroze and continued ok. This was the second install I attempted with di-rc2 with my 'Chic, Optical Faerie' mouse on my Machine: Motherboard: MS5169 Processor:AMD-K6-2/400 400.9Mhz More details about this machine and mouse are specified above. Whilst trying to reproduce the problem symptoms. I am glad to report that this was the first reoccurence. after about a mornings finger poking RC2 install work. I did not come across a symptom instance at all on three install atempts on my Machine: Motherboard: A bit KT7, Raid, 1 Ghz. (details alread given above.) but then at his time, I was not using the same screen that Example 10, uses. If I had to guess from the zero feedback I receive, I would speculate that someone had addressed my earlier reports with 'one to one' use of a 'widget library' and maybe fixing each screen, some thing has improved. as apposed to fixing a single method in a Widget Library or somewhere, which would have resolved all occurences, and I would not be reporting this Symptom Example 10, here. Again, this is only speculation from my outside observations. There is the option that nobody has addressed the source of the error yet (Not a problem to me), I must say that I was pleasantly surprised that I could NOT reproduce the symptoms in the heavily used area of the install process such a the 'Partioning' screens to date in di-RC2. I could easily reproduce the symptoms in previous di Beta1, Beta2 and RC1. Rhetorical: Is there anybody there ? This software is getting better. Well done. It would give me satisfaction to know what code area is involved. Regards McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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; https://ata.wiki.kernel.org/index.php/Pata_hpt37x 'HighPoint 370 series PCI ATA Controllers'. # lsmod shows Module hpt366 size 8535 used by 6. is installed, not Pata_hpt37x Boot method: DVD graphical installer setting up for booting, using an array called /dev/md0 built from two hard drive disks, configured for raid1 mirroring mode. Image version: URL to dvd image downloaded, Official snapshot i386 dvd binary1 20110108-16:28. Only the first DVD 1 of the set is required. Began installing Date: 08 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz. Processor: AMD AThlon K7, 850 Mhz, Socket 'A' Memory:SDRAM 2 x 512Mb = 1Gb. Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level. CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, (why not just try the same disk again) Boot other device: disabled. Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled. Two additional IDE channels provide the capability of adding high performance device(s) to system. IDE HDD Block Mode:Enabled. for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid) Is not used by me for 'hardware raid '. The intention is to use the HPT370 for Debian GNU/Linux MDADM Software raid1 mode (mirroring) using Debian-GNU/Linux-Squeeze-di-RC1-i386 . Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402 HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY STATUS shows no array or devices. Good! I am not using any raid function for this boot, just using it as an additional, fast, IDE controller. Screen button F1 toggles the view CHANNEL STATUS which shows the devices: DASD: Quantity two: IBM-DTLA-307030 drives, primary master and secondary master, Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the HPT370 controller. Good! HPT370 Bios Setting Utility option 7. Set Boot Disk: I have set no disk as Boot Disk here, I will check later. I believe the 'Linux Software Raid Array' is the place to specify /dev/md2 my /boot partition as bootable in partition manager, which I have set. IDE Primary master: none. IDE Primary slave: Pioneer DVD-ROM ATAP. IDE Secondary master: LITE-ON LTR-16102B DVD rewriter. IDE Secondary slave:none. Partitions: df -Tl df: invalid option --'T' BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary. usage: df [-Pkmh] [FILESYSTEM]... df -h Filesystem Size Used Available Use% Mounted on tmpfs505.4M 92.0k 505.3m 0% /dev /dev/md126.6G 473.6m 24.8g 2%/target /dev/md292.0M 17.5M 69.7M20% /target/boot /dev/md126.6G 473.6M 24.8G 2% /dev/.static/dev tmpfs505.4M 92.0K 505.3M 0% /target/dev Base System Installation Checklist: [O] = OK. [E] = Error Initial boot: [O] Detect network card: [O] Configure network: [N/A] Detect CD: [O] Load installer modules:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system: [O] Configure Package Manager: Scanning DVD set disk, Binary-1 only ? (yes) Clock/timezone setup:[O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install:[E] Won't auto boot into new installed system. Comments/Problems: Debian-squeeze-di-RC1-i386 maybe installing the wrong driver hpt366 ? for Highpoint hpt370 raid controller. I do not know which piece of software is responsible to select the GNU/Linux Pata_hpt37x driver ? https://ata.wiki.kernel.org/index.php/Pata_hpt37x 'HighPoint 370 series PCI ATA Controllers'. The same symptoms since installing Beta1, Beta2 and now Debian-squeeze-di-RC1-i386 Release Candidate 1. (jump to my summary “Finally...” at the end of this entry below and return here.) I have yet to acheive taking off the machine, my saved debug logs for bug reporting. I am unsuccesfully trying to mount and will then save to a usb thumbdrive in abscence of a floppy drive. Be aware, these are hand typed excerpts reports only :- I use the 'Graphical Installer' from a down loaded iso image Binary1, cut and verified to a single DVD. After a succesfull install, but unsucessful re booting
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 bit KT7, Raid, 1 Ghz. Processor: AMD AThlon K7, 850 Mhz, Socket 'A' Memory: SDRAM 2 x 512Mb = 1Gb. Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. (Further details of this machine are already reported previously above.) Comments/Problems: Example 1: The [Go Back] screen button icon also does not do it's job always. From the Screen: 'Partition Disks','This is an overview of your currently configured partitions and mount points'. I selected my blue line #1 158 GB ext3. I positioned the mouse screen cursor pointer tip in the centre of the letter 'o' in the screen [Go Back] button icon. I pressed the left mouse button, the icon greyed out, my selected line turned a darker blue. The process went into a wait (froze). I wrote these notes up. I waggled the mouse slightly, while the cursor pointer was still contained inside the button icon borders. The software [Go Back] process then proceeded to continue to the next screen OK. Example 2: Another [Continue] screen button icon not working this time with this THIRD mouse type. Screen: 'Partition Disks','Partition Settings'. Selected blue line: 'Done setting up the partition'. Clicked left mouse button on the small hole in the letter 'e' in [Continue] The continue button icon greyed out, the slected line turned a darker blue, the process did not continue. I wrote up my notes, microwaved my cold tea, waggled the mouse, the process continued OK. Example 3: No problems (so far) with the [Help] button icon. Screen: 'Partition Disks','This is an overview of your currently configured partitions and mount points'. The [Help] button icon was tried 21 times at this screen with no issue, problem or faiilures. Example 4: No problems (so far) with the [Screen Shot] (Screenshot) button icon. Screen: 'Partition Disks','This is an overview of your currently configured partitions and mount points'. The [Screenshot] button icon was tried 20 times at this screen with no issue, problem or failures. Example 5: The [Continue] screen button icon failed to do it's job on an occurence of; Screen: 'Save debug logs','Mounted file system. [Continue]. The selected line turned darker blue, the continue button icon greyed out. The process did not continue. I wrote up my notes, waggled, the process continued OK. Off topic Note: rm removing most of my 'saved debug logs' ( after, I am guessing, saving 5 logs) I bypassed a problem I encountered, and I could then resume saving debug logs without error. I was saving to and I entered /target/var/log/ # nano /target/var/log/install/syslog showed; Errors were encountered while processing: python-central E: Sub-process /usr/bin/dpkg returned an error code (1) Example 6: 14.01.2011. I changed to a 4th? mouse, to a Compaq branded suznou Logitech Electronics Ltd, ASSY P/N 334684-108 2001.04.12 38920101 Two button, mouse ball, scroll wheel, PS/2 plug. On machine: Motherboard: A bit KT7, Raid, 1 Ghz. (Further details -less mouse- of this machine are already reported previously above.) I started a debian squeeze di RC1 i386 binary 1 DVD install session. I had an occurence of [Continue] failing, on Screen: 'Set up users and passwords','?enter password?' a little waggle took me to 'A user account will be created for you to use...' Proceeded OK. Example 7: [Go Back] failed at Screen: 'Finish the installation','Installation complete'. 1) I wish GoBack would indicate where it was going to. It varies from; di-mm screen, to, where it came from. 2) Ouch, A spacebar tap to free screensaver, was taken by di as a [Continue]. Example 8: [GoBack] failed at Screen: 'Save debug logs','Mounted file system'. [GoBack], failure, waggle, to screen: 'Directory in which to save debug logs', OK. Example 9: New start RC1 install, Screen Partition Disks','?Choose method?' [Continue] failed (Froze), waggled, the process proceeded to continue OK. In summary, The issue symptom reproduces on Multiple machines with multiple mice, on at least two screen button icons; [Go Back] and [Continue]. I wonder what the library is called that supplies the screen widget software ? di is great software getting greater. My regards to all involved, McTech. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 machine has a reasonable amount of install processing to do.
My scenario was another squeeze-di-beta2-i386 install on the same machine :-
('A bit' KT7, Raid, 1 Ghz.AMD AThlon K7, 850 Mhz, SDRAM 1Gb.Award
Modular Bios v6.00. Via KT 133 ATX, Hipoint HPT370 raid controller.)
The first occurence of the symptom occured this time, at the
Partition Manager stage.
Screen: 'Partition Disks','Done setting up the partition' line was
selected and highlighted,
with the mouse cursor pointer arbitrarily positioned on the dot of
the letter 'i' of the [Continue] screen icon.
The [Continue] icon greys out, the selected line goes to dark red.
The new observation is, that this is the correct operation, until
this specific processing completes.
It could take a while in a good working situation, lets say 20
seconds, or longer or shorter, and then the screen flicks correctly to
the next task at hand,
depending what processing needs to be done.
The majority of the observation is correct and 'Working as coded' and
as we would like.
The 'Fault symptom' is when this action stays frozen for half an
hour, and would be longer,
if you do not realise you have to trigger the process resumption by
waggling the mouse a little bit and therefore instantaneously freeing
up
the processing by - I guess - exiting a wait loop maybe.
---
Replication and observations of the fault symptom on a DifferenT
machine, 08.01.2011.
Mouse: Optical USB Lenovo, three button and a scroll pressure thingy,
Part number: 24P0494 IBM FRU P/N 24P0495 Model: MO09BO IBM Scroll Point.
which has been working adequately for, I don't know, 6 years maybe ?
on Debian OS's going back at least four Toy Story Characters.
It is now on the end of a KVM to three machines, except when I am
using this mouse without a KVM mainly for this fault replication
Machine: Motherboard: MS5169
Processor:
AMD-K6-2/400400.9Mhz
Memory:
Memtest86+ v4.10 224MB pass:1 errors:0
Bios:
American Megatrend AMIBIOS 1996 A5169MS v2.6 121598
51-1215-00-0011-071595-41E_43C-MS5169-T99-H
DASD pci board: Manufacturer:
For Best Ports Connection (Is the manufacturers name.)
Sil 3114 sata raid bios version 5.3.14 2006.
Serial ATA host controller card SA3114-41R 4 port.
chip: Silicon Image chip StealVine Sil 3114 CTU.
printed on the chip: QG6332.1-10644AD03AX2.
printed on the sata pci board: SATA3114-A01
Extra detail:-
Motherboard:
MicroStar MS5169-T99-0 www.msi.com.tw
Chipset:
Screen printed on motherboard: MS5169 Ver 3 AL9.
Book in new unopened box: Aladdin AL9, V2.1 B manual revision.
Screenprinted on Chipset Aladdin 5 M1531 / M1543.
Memory:
SDRAM PC100 DIMM, No Parity, Non ECC.
Fault Scenario :- debian-squeeze-di-beta2-i386 install.
Graphical Installer.
Screen: 'Configure the network','Do not configure the network at this time'.
[Continue] (OK) 'Please enter the host name for this system'
I left the default debian host name in the field.
[Continue] randomly choosing to place the mouse cursor on the dot of
the letter 'i' in the Continue icon, which, on pressing the left mouse
button greyed out the Continue icon and darkened the red line
selected. Eventually after pencil writing up this report, I moved the
mouse cursor minimally (let's say 1 mm) with the mouse cursor still
inside the Continue icon frame, and the programme continued
satisfactorily.
Note: this is all on a DifferenT machine to the original bug report,
with a different a bios and chipset manufacturer, etc.
I selected the [Go Back] screen icon and replicated the fault symptom
again in the same place -'Please enter hostname for this system'.- I
could not replicate when I went [GoBack] then [Continue] for attempts
3,4,5. It did replicate the symptom on attempt 6 and froze in exactly
the same place.
Try 7: I selected icon [Go Back], On Screen:'Debian Installer Main
Menu','Configure the network',[Continue] froze, write it up, waggle,
OK!
Try 8: 'Debian Installer Main Menu','Execute a shell' [Continue]
Froze, write it up, waggle, OK!
Try 9: 'Execute a shell' [Continue] selected with mouse OK,
'Interactive shell' [Continue] Busy Box V1.17.1, worked OK!
Try 10: Screen: 'Partition Disks', 'Write changes to disk' [Continue]
with mouse cursor pointing to the centre of the letter 'o' on
Continue. (I fancied a change) pressed left button mouse, the process
Froze. I penciled wrote this report up, Waggled the mouse cursor 1
milimetere, still in the icon framework, the process continued to work
OK!
Try 11: With the objective to get the install debug log saved and off
the machine.
At Screen: 'Install the base system','Not installing to unclean
target' (On purpose) [Go Back] 'Installation step failed'
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 sticky hardware buttons on the multiple mice maybe ? 1.) Greyed out for button pressed, and 2.)'Programme action' when button realeased. Just a thought. I could try to multiple press and click of the left button, without moving the mouse in the plain. 2010.12.10. I noticed this MINOR issue again, this time on Debian squeeze di Beta2 (Beta 2) (Beta-2) at the Partition Disks: Partition Settings: screen. Though the issue symptom may have occured earlier. I do not really know. I will keep looking. After setting up a raid1 mirroring array with 3 raid partitions on two hard disks, my last action was setting up the /boot partition on the array when I experienced the 'freeze'. Selecting the task 'Finish partitioning and write changes to disk' I went to press [CONTINUE] My [CONTINUE] button icon, on my install screen, has this issue of having a 'Two Trigger' attribute. Using a different mouse this time. Not the USB optical mouse I originally used. This time I am using, for fault finding, an original IBM PS/2 mouse, part number IBM 6450350. Left button click and the [CONTINUE] button icon on the screen GREYs out. Good. OK. I can then leave the mouse untouched for as long as I like, without any other programme reaction. Frozen. The [CONTINUE] button screen icon remains 'greyed out', without any programme action that I selected. I then eventually moved the mouse in the horizontal plane slightly and the programme reacts to the [continue] button icon being pressed, and the task completes OK. Next time, I should try the vertical plane. I selected the [GO BACK] screen icon button and followed up reproducing the symptom issue with the [continue] button icon. After selecting 'Finish partitioning' yet again and going to the 'Write changes to the disk' again, I could NOT reproduce the 'Two Trigger' issue on the [continue] icon button. The icon button worked OK, UNTIL I reached the 'Software selection' screen. I went to accept the default software selection GDE and SSU. I pressed the left button with the cursor on [CONTINUE] and the issue returned. On purpose, I placed the tip of the 'cursor arrow pointer' on the coordinates; X: The gap Horizontally, Halfway between the left hand vertical side of the [continue] screen icon button's box frame, and it's letter 'C' the first letter in [continue], and... the Y: coordinate, Vertically halfway up or down the [continue] icon box frame. I now have to correct my earlier description in my first posting. On purpose, I did NOT move the cursor outside the box frame of the [continue] icon. Eventually, I moved the mouse the tinyest amount I could, lets say one millimetre. While still well inside the icons box framework, the programme action was triggered OK, whilst the cursor pointer was still inside the icon. I wrongly said previously, that I had to move the cursor outside the icons boundaries for some programme action. Having reproduced the symptom of this MINOR issue to this degree, I now feel a total pedant. Pragmatically, I can live with this particular issue. Best of luck, I wish you all well. Thank you for all the GREAT software, everybody involved. I really do appreciate Debian, et al, your efforts and your support, In the past and in the future. Happy holidays. 2010.12.17. Regards, McTech. ---end.
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: issue-report_No-boot-from-Sil3114-SATA-drive-on-di-beta2-i386-20101209.utf Date: 10 December 2010. Boot method: DVD install. Image version: Full URL to image downloaded. Only the first DVD 1 of the set to test. Machine:Motherboard: MS5169 Processor: AMD K-6-2/400 400.9Mhz Memory: Memtest86+ v4.10 224MBpass:1 errors:0 Chipset: Bios: American Megatrend AMIBIOS 1996 A5169MS v2.6 121598 51-1215-00-0011-071595-41E_43C-MS5169-T99-H DASD pci board: Manufacturer: For Best Ports Connection Sil 3114 sata raid bios version 5.3.14 2006. Serial ATA host controller card SA3114-41R 4 port. chip: Silicon Image chip StealVine Sil 3114 CTU. printed on the chip: QG6332.1-10644AD03AX2. printed on the sata pci board: SATA3114-A01 FG-SA3114-4IR-01-BC01 or it might be: FG.SA3114.4IR.01.BC01 I use this card for the fast disk control bus and future proofing, by buying sata and not pata. DASD: The only hard disk drive in the machine: 160GB sata ST3160815AS drive 0. I might use the Linux Debian MDADM Software raid 1, if and when I can get that far into the 'debian squeeze' install. BIOS: AMIBIOS HIFLEX setup utility v1.21 1998 American Megatrends. Standard cmos setup:Screen 1. Fast Boot bypasses filesystem checkup ( currently on.) Base memory: 640KB Extd memory 223 MB 229,376KB Advanced CMOS setup:Screen 2. ( SCSI works. Was IDE0 for the old pata disk. IDE 0 to 3.) 1st Boot device:CD-ROM 2nd Boot Device:SCSI ( As written in the Sata raid pci Board user manual.) 3rd Boot Device:Disabled. 4th Boot Device:Disabled. Try other Boot Devices?: NO. ( I tried yes and it did not recognised the SATA board.) Boot to OS/2:NO. Advanced Chip Set Up: Screen . Nothing of interest here. PCI / Plug and play setup: Screen . Plug and play aware O/S: Yes Offboard PCI IDE CARD?: AUTO bios on reboot: PCI devices: Slot 4 RAID: IRQ9 Manufacturer: For Best Ports Connection IDE Primary master:CDROM Pioneer DVD-RW DVR-110. ( I use this all the time.) IDE Primary slave: Not installed. IDE Secondary master: Not installed IDE Secondary slave: LiteOnIt.com.tw ATAPI CD-ROM Drive 36x. BIOS: Boot Sector Virus Protection: triggers when I use Grub Disks :- Grub Rescue disk grub-0.95-i486-pc.iso 30.07.2007 Super Grub Disk SGD_0.9590.iso 31.07.2007 Grub Super Disk RESCATUX v0.21 Hybrid 07.12.2010 RESCAPP All grub iso disk images I obtained, are from I believe to be the original source Uri's and I MD5SUM checked. The Boot Sector Virus Protection has been enabled during 'Debian Squeeze di Beta2' install and has been disabled during my latest install attempts. Transguard v? I think. I will check. BSVP is currently OFF (disabled) with no difference to the symptom. Yes, I know I must and want to, enable protection eventually. I will look deeper into this separate BSVP issue later. I have no data on this machine. Partitions: During a successful squeeze-di-Beta2-i386 install up until the auto re boot. Partition Disks SCSI 1 (0,0,0,) (sda) - 160 GB sda # 1 primary 158.5 gb Bootable Format ext3/ ( after swap space) sda # 5 logical1.5 gb Not bootable Format swap /swap ( begining of disk space) sda # 3 primary 99.5gb Bootable Format ext3/boot ( end of disk space) I believe swap space should come first (quickest to get to) especially on a small RAM machine. if it starts swapping you want swap to be quick to get to. Thrash me if I am wrong. Base System Installation Checklist: [O] = OK. [E] = Error Initial boot: [O] Detect network card:[O] Configure network: [N/A] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Configure Package Manager: Scanning DVD set disk, Binary-1 only. (yes) Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader: [O] Overall install: [E] Won't auto boot into new installed system, at end of install process. Installing from debian squeeze di b2 i386 Bin-1 ( Beta 2,
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 downloaded. Only the first DVD 1 of the set is required. Date: 09 December 2010. Installing from debian squeeze di b2 i386 Bin-1 ( Beta 2, Beta-2 ) gives the same symptoms as Beta-1 install :- Using graphical installer: Scan another CD or DVD? (No) ( I used the first dvd only, to reproduce the symptom.) I am trying to boot from a raid 1 (mirror) set, md2 = /boot, md0 = /swap, md1 = /. See above for details. I installed the GRUB boot loader to the master boot record. Finish the installation : Installation complete, so it is time to boot into your new system... The hardware post and bios progress ok. When the bios hands over to continue the ipl from a hard disk it seems unsuccessful, it just waits. *** This is where the install fails. It does not boot up into the newly installed system. *** I repeated the install up to, but not setting passwords, to the dd-mm (Debian Installer-Main Menu) to: Check the CD-ROM(s) integrity. (On the same target machine.) Integrity test successful. The CD-ROM is valid. The squeeze di b2 i386 Bin-1 dvd integrity passed ok. Thank you for any help to get my raid 1 booting. Regards, McTech.
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 determination,and to see if it worked ok, as my other submissions seem to be getting through ok.I hope my resend of detail helps someone. It is meant to. I am new to this and I am learning. I will see and learn where I should post resends. To either my original bug#606227 or reasigned bug#602421. I know not both in future. In case of formatting issues again; Composed in OpenOffice .odt v3.1.0 , emailed with Firefox 3.6.8 )---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.odt Boot method: DVD install.Image version: Full URL to image downloaded. The first two DVD's of the squeeze-di-Beta-1-i386 set only.Date: 06 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz.Processor: AMD AThlon K7, 850 Mhz, Socket 'A'Memory:SDRAM 2 x 512Mb = 1Gb.Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level.CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, Boot other device: disabled.Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled.Two additional IDE channels provide the capability of adding high performance devie(s) to system. IDE HDD Block Mode: Enabled.for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid)Not used by me for 'hardware raid'. The HPT370 is used by me, only for the fast disk control bus.Linux Debian MDADM Software raid will be used when I can get that far into the 'squeeze-di-Beta1' install. Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY STATUS shows no array or devices. Good! screen button F1 toggles the view CHANNEL STATUS which shows the devices:DASD: quantity two: IBM-DTLA-307030 drives, primary master and secondary master, Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the HPT370 controller. Good!HPT370 Bios Setting Utility option 7. Set Boot Disk: I have set no disk as Boot Disk here,as I believe the 'Linux Software Raid Array' is the place to specify /dev/md2 /boot as bootable in partition manager, which I have set. IDE Primary master: none.IDE Primary slave: Pioneer DVD-ROM ATAP (I do not use this.)IDE Secondary master: LITE-ON LTR-16102B DVD rewriter (I use this all the time.)IDE Secondary slave: none. Partitions: df -Tl df: invalid option --'T'BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary. usage: df [-Pkmh] [FILESYSTEM]...df -hFilesystem SizeUsedAvailable Use%Mounted on tmpfs 505.4m 92.0k 505.3m 0% /dev/dev/md1 26.6g 473.6m 24.8g 2% /target/dev/md2 92.0M 17.5M 69.7M 20% /target/boot/dev/md126.6G 473.6M 24.8G 2% /dev/.static/devtmpfs 505.4M 92.0K 505.3M 0% /target/dev Output of lspci -nn00:00.0 Host Bridge [0600] Via Technologies ... (rev 02)00:01.0 PCI Bridge [0604] ... AGP 07.0 ISA bridge... Appollo Super South ... (rev 22) 07.1 IDE ... PIPC Bus Master IDE ... (rev 10) 07.2 USB Controller [0c03]: Via Technologies VT82x UHCI USB1.1 Controller ... (rev 10) 07.3 USB1.1 Controller ... (rev 10) 07.4 BridgeVT82c686 [Appollo Super ACPI]... (rev 30) 11.0 Ethernet controller ...00:13.0 Mass storage controller [0180]: HighPoint Technologies, Inc. HPT ... /370/ ... [1103:00041] (rev 03)01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:47421] (rev 5c) Base System Installation Checklist:[O] = OK. [E] = Error Initial boot: [O]Detect network card:[O]Configure network: [N/A]Detect CD: [O]Load installer modules: [O]Detect hard drives: [O]Partition hard drives: [O]Install base system:[E] Configure Package Manager: Scanning DVD set disks, Binary-2. Clock/timezone setup: [ ]User/password setup:[ ]Install tasks: [ ]Install boot loader:[ ]Overall install:[E] Comments/Problems: I
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 sole email, an automated reply sitting in my inbox since my submission back in 05th October 2009. I have resubmitted this bug and patch to include the detail I had gleaned, in case it helps someone. I am learning how the bug reports system works, allbeit slowly. sorry for my delay. I am unsure whether to send to sub...@bugs.debian.org or attach to 552...@bugs.debian.org I will soon see from the effect. I know that both is wrong. I am learning. Sorry for any inconvieniance. *** An error occurred The following details are provided: E: asterisk: subprocess installed post-installation script returned error exit status 1 Setting up asterisk (1:1.6.2.0~dfsg~beta3-1) ... insserv: Service zaptel has to be enabled to start service asterisk insserv: exiting now! The configuration script is throwing a zaptel missing dependency. but zaptel is no more. I believe It should be Recommends: dahdi OR dahdi-linux. The changelog shows:- http://packages.debian.org/changelogs/p ... /changelog Debian Changelog asterisk (1:1.6.2.0~dfsg~beta3-1) 2009 asterisk (1:1.6.2.0~dfsg~beta3-1) unstable; urgency=low [ F L ] * New upstream release. * Remove init script's zaptel-fix action; there's no zaptel any more and was also lintian-buggy in its current form. * Install Zaptel-to-DAHDI.txt, explains the migration procedure from Zaptel to DAHDI and is therefore useful when upgrading from lenny. MY PATCH: I altered a line in file: /etc/init.d/astersisk From: # Required-Start: $local_fs zaptel To: # Required-Start: $local_fs dahdi dahdi-linux Then, # dpkg --configure --force-all asterisk # dpkg --status asterisk Package: asterisk Status: install ok installed = There is more detailed information in my previous work on this issue at : http://forums.debian.net/viewtopic.php?f=5t=44390 I have uninstalled and reinstalled and have identified this potential bug is also in asterisk 1.6.2.0~dfsg~rc1-1 . However I am having many other separate problems which I am diligently but ploddingly resolving. This stops me from testing asterisk quick enough to my satisfaction, to get this potential bug processed. My concern with my patch is, should I specify just one module; dahdi or dahdi-linux ? although specifying both does install asterisk with dahdi ok. but no sign in the dependancies shown below, of dahdi-linux. It depends on what you actually want. My next job is to strip out all the 96 sample configurations somehow, to make asterisk 1.6 useable for a newbie with starter books such as my book, Asterisk,the future of telephony. or the book to be published in January 2010 Practical Asterisk 1.4 and 1.6: From Beginner to Expert to allow me to operate asterisk further, and to test for the effectiveness of my patch. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages asterisk depends on: ii adduser 3.111add and remove users and groups ii asterisk-config 1:1.6.2.0~dfsg~rc1-1 Configuration files for Asterisk ii asterisk-sounds-mai 1:1.6.2.0~dfsg~rc1-1 Core Sound files for Asterisk (Eng ii dahdi 1:2.2.0~rc3-1utilities for using the DAHDI kern ii libasound2 1.0.21a-1shared library for ALSA applicatio ii libc-client2007b8:2007b~dfsg-1.1+b1 c-client library for mail protocol ii libc6 2.9-26 GNU C Library: Shared libraries ii libcap2 1:2.16-5 support for getting/setting POSIX. ii libcurl37.19.5-1.1 Multi-protocol file transfer libra ii libgcc1 1:4.4.1-4GCC support library ii libglib2.0-02.22.0-1 The GLib library of C routines ii libgmime-2.0-2a 2.2.22-4 MIME library ii libgsm1 1.0.13-1 Shared libraries for GSM speech co ii libiksemel3 1.2-4C library for the Jabber IM platfo ii libldap-2.4-2 2.4.17-2 OpenLDAP libraries ii liblua5.1-0 5.1.4-3 Simple, extensible, embeddable pro ii libncurses5 5.7+20090803-2 shared libraries for terminal hand ii libnewt0.52 0.52.10-4Not Erik's Windowing Toolkit - tex ii libogg0 1.1.4~dfsg-1 Ogg bitstream library ii libopenais2 0.83-1 Standards-based cluster framework ii libpopt01.14-4 lib for parsing cmdline parameters ii libpq5 8.4.1-1
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 the first DVD 1 of the set is required. Date: 08 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz. Processor: AMD AThlon K7, 850 Mhz, Socket 'A' Memory:SDRAM 2 x 512Mb = 1Gb. Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level. CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, Boot other device: disabled. Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled. Two additional IDE channels provide the capability of adding high performance device(s) to system. IDE HDD Block Mode:Enabled. for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid) Not used by me for 'hardware raid'. The HPT370 is used by me, only for the fast disk control bus. Linux Debian MDADM Software raid is set up in the partition manager during 'squeeze-di-Beta1' install. Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402 HPT370 BIOS Setting Utility: The screen button F1 toggles the view ARRAY STATUS shows NO array or devices at this time. Good! The screen button F1 toggles the view CHANNEL STATUS which shows the real hardware DASD: DASD: Quantity two: IBM-DTLA-307030 drives, primary master and secondary master, Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the HPT370 controller. Good! HPT370 Bios Setting Utility: Option 7. Set Boot Disk: I have set no disk as Boot Disk here, as I believe the 'Linux Software Raid Array' is the place to specify /dev/md2 /boot as bootable in partition manager, which I have since set. IDE Primary master: none. IDE Primary slave: Pioneer DVD-ROM ATAP (I do not use this.) IDE Secondary master: LITE-ON LTR-16102B DVD rewriter (I use this all the time.) IDE Secondary slave:none. Partitions: df -Tl df: invalid option --'T' BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary. usage: df [-Pkmh] [FILESYSTEM]... df -h Filesystem SizeUsedAvailable Use%Mounted on tmpfs 505.4m 92.0k 505.3m 0% /dev /dev/md126.6g 473.6m 24.8g 2% /target /dev/md292.0M 17.5M 69.7M 20% /target/boot /dev/md126.6G 473.6M 24.8G 2% /dev/.static/dev tmpfs 505.4M 92.0K 505.3M 0% /target/dev Output of lspci -nn 00:00.0 Host Bridge [0600] Via Technologies ... (rev 02) 00:01.0 PCI Bridge [0604] ... AGP 07.0 ISA bridge... Appollo Super South ... (rev 22) 07.1 IDE ... PIPC Bus Master IDE ... (rev 10) 07.2 USB Controller [0c03]: Via Technologies VT82x UHCI USB1.1 Controller ... (rev 10) 07.3 USB1.1 Controller ... (rev 10) 07.4 BridgeVT82c686 [Appollo Super ACPI]... (rev 30) 11.0 Ethernet controller ... 00:13.0 Mass storage controller [0180]: HighPoint Technologies, Inc. HPT ... /370/ ... [1103:00041] (rev 03) 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:47421] (rev 5c) Base System Installation Checklist: [O] = OK. [E] = Error Initial boot: [O] Detect network card:[O] Configure network: [N/A] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Configure Package Manager: Scanning DVD set disk, Binary-1 only. (yes) Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Won't auto boot into new installed system. --- /var/log/syslog excerpt 2010 :- Dec 8 11:39:18 kernel: [ 486.432151] md: md2 stopped. Dec 8 11:39:18 kernel: [ 486...] bindhdg1 Dec 8 11:39:18 kernel: [ 486...] bindhde1 Dec 8 11:39:18 kernel: [ 486...] raid1 personality registered for level 1 Dec 8 11:39:18 kernel: [ 486...] raid1: raid set md2 active with 2 out of 2 mirrors Dec 8 11:39:18 kernel: [ 486...] md2: detected capacity change from 0 to 99602432 Dec 8 11:39:18 md-devices: mdadm: /dev/md/2 has been started with 2 drives. Dec 8 11:39:18 kernel: [ 486...] md2: Dec 8 11:39:18 kernel: unknown partition table === *** Is this the start of my
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 of the set only.Date: 06 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz.Processor: AMD AThlon K7, 850 Mhz, Socket 'A'Memory:SDRAM 2 x 512Mb = 1Gb.Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level.CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, Boot other device: disabled.Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled.Two additional IDE channels provide the capability of adding high performance devie(s) to system. IDE HDD Block Mode: Enabled.for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid)Not used by me for 'hardware raid'. The HPT370 is used by me, only for the fast disk control bus.Linux Debian MDADM Software raid will be used when I can get that far into the 'squeeze-di-Beta1' install. Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY STATUS shows no array or devices. Good! screen button F1 toggles the view CHANNEL STATUS which shows the devices:DASD: quantity two: IBM-DTLA-307030 drives, primary master and secondary master, Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the HPT370 controller. Good!HPT370 Bios Setting Utility option 7. Set Boot Disk: I have set no disk as Boot Disk here,as I believe the 'Linux Software Raid Array' is the place to specify /dev/md2 /boot as bootable in partition manager, which I have set. IDE Primary master: none.IDE Primary slave: Pioneer DVD-ROM ATAP (I do not use this.)IDE Secondary master: LITE-ON LTR-16102B DVD rewriter (I use this all the time.)IDE Secondary slave: none. Partitions: df -Tl df: invalid option --'T'BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary. usage: df [-Pkmh] [FILESYSTEM]...df -hFilesystem SizeUsedAvailable Use%Mounted on tmpfs 505.4m92.0k 505.3m 0% /dev/dev/md1 26.6g 473.6m 24.8g 2% /target/dev/md2 92.0M 17.5M 69.7M 20% /target/boot/dev/md1 26.6G 473.6M24.8G 2% /dev/.static/devtmpfs 505.4M92.0K 505.3M 0% /target/dev Output of lspci -nn00:00.0 Host Bridge [0600] Via Technologies ... (rev 02)00:01.0 PCI Bridge [0604] ... AGP 07.0 ISA bridge... Appollo Super South ... (rev 22) 07.1 IDE ... PIPC Bus Master IDE ... (rev 10) 07.2 USB Controller [0c03]: Via Technologies VT82x UHCI USB1.1 Controller ... (rev 10) 07.3 USB1.1 Controller ... (rev 10) 07.4 BridgeVT82c686 [Appollo Super ACPI]... (rev 30) 11.0 Ethernet controller ...00:13.0 Mass storage controller [0180]: HighPoint Technologies, Inc. HPT ... /370/ ... [1103:00041] (rev 03)01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:47421] (rev 5c) Base System Installation Checklist:[O] = OK. [E] = Error Initial boot: [O]Detect network card:[O]Configure network: [N/A]Detect CD: [O]Load installer modules: [O]Detect hard drives: [O]Partition hard drives: [O]Install base system:[E] Configure Package Manager: Scanning DVD set disks, Binary-2. Clock/timezone setup: [ ]User/password setup:[ ]Install tasks: [ ]Install boot loader:[ ]Overall install:[E] Comments/Problems: I came across three squeeze-di-beta1 issues, and two wish list items.I will report them in seperate reports.(Issue 1 of 3.) Using graphical installer:Screen title: Configure the package manager---The CD or DVD with the following label has been scanned:Debian GNU/Linux squeeze-di-beta1_Squeeze_-Official Beta i386 DVD Binary-1 20101027-01:46If you wish to scan another CD or DVD, please insert it now.Scan another CD or DVD? (Yes)---The CD or DVD with the following label has been scanned: If you wish to scan another CD or DVD, please insert it now.Scan another CD or DVD? (No, as I only have two DVD's to install on purpose.)---Note: Did you notice that the Binary-2 label was missing on that last
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: DVD install. Image version: Full URL to image downloaded. The first two DVD's of the set only. Date: 06 December 2010. Machine: Motherboard: A bit KT7, Raid, 1 Ghz. Processor: AMD AThlon K7, 850 Mhz, Socket 'A' Memory:SDRAM 2 x 512Mb = 1Gb. Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A', FSB 200Mhz, AGP 4X. Updated bios: Award Modular Bios v6.00 PG. 07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level. CMOS Set Up Utility: Advanced BIOS features: First boot device: CDROM, Second boot device: ATA100RAID, Third boot device: ATA100RAID, Boot other device: disabled. Delay for IDE Initial (Secs) 8. Intergrated Peripherals: ATA100RAID IDE Controller: Enabled. Two additional IDE channels provide the capability of adding high performance device(s) to system. IDE HDD Block Mode: Enabled. for automatic detection of the optimal number of block read/writes per sector the drive can support. DASD chip: On-motherboard HPT370 raid controller 2001 www.highpoint-tech.com (hardware raid) Not used by me for 'hardware raid'. The HPT370 is used by me, only for the fast disk control bus. Linux Debian MDADM Software raid will be used when I can get that far into the 'squeeze-di-Beta1' install. Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402 HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY STATUS shows no array or devices. Good! screen button F1 toggles the view CHANNEL STATUS which shows the devices: DASD: quantity two: IBM-DTLA-307030 drives, primary master and secondary master, Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the HPT370 controller. Good! HPT370 Bios Setting Utility option 7. Set Boot Disk: I have set no disk as Boot Disk here, as I believe the 'Linux Software Raid Array' is the place to specify /dev/md2 /boot as bootable in partition manager, which I have set. IDE Primary master: none. IDE Primary slave: Pioneer DVD-ROM ATAP (I do not use this.) IDE Secondary master: LITE-ON LTR-16102B DVD rewriter (I use this all the time.) IDE Secondary slave:none. Partitions: df -Tl df: invalid option --'T' BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary. usage: df [-Pkmh] [FILESYSTEM]... df -h Filesystem SizeUsedAvailable Use%Mounted on tmpfs 505.4m 92.0k 505.3m 0% /dev /dev/md126.6g 473.6m 24.8g 2% /target /dev/md292.0M 17.5M 69.7M 20% /target/boot /dev/md126.6G 473.6M 24.8G 2% /dev/.static/dev tmpfs 505.4M 92.0K 505.3M 0% /target/dev For completmess; /dev/md0 size is 1.something Gb/swap /dev/md1 ext3/ /dev/md2 ext3/bootafter I partition them. Output of lspci -nn 00:00.0 Host Bridge [0600] Via Technologies ... (rev 02) 00:01.0 PCI Bridge [0604] ... AGP 07.0 ISA bridge... Appollo Super South ... (rev 22) 07.1 IDE ... PIPC Bus Master IDE ... (rev 10) 07.2 USB Controller [0c03]: Via Technologies VT82x UHCI USB1.1 Controller ... (rev 10) 07.3 USB1.1 Controller ... (rev 10) 07.4 BridgeVT82c686 [Appollo Super ACPI]... (rev 30) 11.0 Ethernet controller ... 00:13.0 Mass storage controller [0180]: HighPoint Technologies, Inc. HPT ... /370/ ... [1103:00041] (rev 03) 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage Pro AGP 1X/2X [1002:47421] (rev 5c) Base System Installation Checklist: [O] = OK. [E] = Error. [?] I do not know where this started. Initial boot: [O] Detect network card:[?] I do not know where the symptom started. Configure network: [N/A] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[E] For another reason. Overall install:[?] Comments/Problems: I came across three squeeze-di-beta1 issues, and two wish list items. I will report them in seperate reports. (This very minor Issue is 2 of 3.) Using graphical installer: Screen title: Not sure which 'squeeze-di-Beta-1' install screen originally
