Bug#981592: keyboard-configuration: Compose key can not create Greek symbols with altgr-intl layout
Package: keyboard-configuration Version: 1.200 Severity: important Could be that the compose file at /usr/share/X11/locale/en_US.UTF-8/Compose should include the coding for the normal engineering greek symbols via the compose-key? (This is supposed to be the source of the 'compose' key codings (The compose key is labeled to help confuse people)) This at one time we could get these symbols with g or G -- would get us π (PI). There are all sorts of rare charactors in the file - but the Greek letters - like π (PI) - are not assigned a compose key sequence .. instead by a key. If I run xmodmap -pke |grep -i dead_ I see there isn't a greek dead-key assigned. This rather normal set up should allow one to type Greek symbols 'out of the box'. The file at /usr/share/X11/locale/en_US.UTF-8/Compose belongs to libx11-data - but I don't see that it is open? -- System Information: Debian Release: 10.7 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages keyboard-configuration depends on: ii debconf 1.5.71 ii liblocale-gettext-perl 1.07-3+b4 keyboard-configuration recommends no packages. keyboard-configuration suggests no packages. Versions of packages console-setup depends on: pn console-setup-linux | console-setup-freebsd | hurd ii debconf 1.5.71 ii xkb-data2.26-2 Versions of packages console-setup suggests: ii locales 2.28-10 ii lsb-base 10.2019051400 Versions of packages console-setup-linux depends on: ii init-system-helpers 1.56+nmu1 ii kbd 2.0.4-4 Versions of packages console-setup-linux suggests: pn console-setup Versions of packages keyboard-configuration is related to: pn console-common pn console-data pn console-tools pn gnome-control-center ii kbd 2.0.4-4 ii systemd 241-7~deb10u5 -- debconf information: * keyboard-configuration/optionscode: compose:caps * keyboard-configuration/altgr: The default for the keyboard layout debian-installer/console-setup-udeb/title: console-setup/codesetcode: Lat15 * keyboard-configuration/toggle: No toggling * console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages * keyboard-configuration/other: * keyboard-configuration/store_defaults_in_debconf_db: true console-setup/fontsize: 8x16 keyboard-configuration/unsupported_config_options: true keyboard-configuration/unsupported_config_layout: true console-setup/use_system_font: keyboard-configuration/unsupported_layout: true keyboard-configuration/unsupported_options: true * console-setup/fontsize-fb47: 8x16 console-setup/framebuffer_only: * console-setup/charmap47: UTF-8 * keyboard-configuration/layoutcode: us * keyboard-configuration/layout: * keyboard-configuration/modelcode: microsoft4000 * keyboard-configuration/switch: No temporary switch * keyboard-configuration/model: Microsoft Natural Ergonomic 4000 * keyboard-configuration/variant: English (US) - English (intl., with AltGr dead keys) * keyboard-configuration/variantcode: altgr-intl * keyboard-configuration/xkb-keymap: us(altgr-intl) console-setup/guess_font: * keyboard-configuration/ctrl_alt_bksp: false console-setup/fontsize-text47: 8x16 * console-setup/fontface47: Fixed console-setup/store_defaults_in_debconf_db: true * keyboard-configuration/compose: Caps Lock
Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios
On 03/02/2014 03:23 PM, Cyril Brulebois wrote: Control: tag -1 - d-i squeeze This is from quite a while ago - There have been changes to grub2 and many other tools in the mean time. There are two issues - one is bios limitations on some MBs and the other is the need to use GPT for the partition table on large TB drives. I have some notes on this here: http://wiki.xtronics.com/index.php/EFI_UEFI_GUID_GPT_and_large_TB_partitions One can sometimes work around the BIOS issues by changing to coreboot on supported MBs. I have not tested this with wheezy as my preferred set up now uses a raid of SSHDs for the / (system files) and only /home is on the large drives. Your question should be if the install images support GPT - and that I don't know. Hope I've helped. Hi Karl, Karl Schmidt k...@xtronics.com (2011-09-22): This is failing with the current squeeze installer that uses grub2. What I don't know is if this is possibly a BIOS issue - my understanding is that Debian takes over and uses its own driver. This is on a Tyan S7002 which uses: # lspci |grep SATA 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller for the SATA controller. I'm attempting a workaround - I'm installing the main system on a 40GB raided pair of SSD and will have /homes on large ( 2.18TB ) drives. I will partition the large drives with gparted and use GPT. are you experiencing similar issues with wheezy installation images? Mraw, KiBi. -- Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 History may not repeat itself, but it does rhyme a lot. -Mark Twain -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5313db2a.7060...@xtronics.com
Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios
This is failing with the current squeeze installer that uses grub2. What I don't know is if this is possibly a BIOS issue - my understanding is that Debian takes over and uses its own driver. This is on a Tyan S7002 which uses: # lspci |grep SATA 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller for the SATA controller. I'm attempting a workaround - I'm installing the main system on a 40GB raided pair of SSD and will have /homes on large ( 2.18TB ) drives. I will partition the large drives with gparted and use GPT. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Merchandise offered without a price, is sure to cost more than it is worth. -kps -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e7b7e1a.2030...@xtronics.com
Bug#642179: debian-installer: Installs on drives larger than 2.19TB fails with older bios
Package: debian-installer Version: 20110106+squeeze3 Severity: normal Tags: d-i squeeze -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Install attempts on a Tyan S7002 failed with a drive larger than 2.19TB (would fail at the grub installation) I was able to move an install to a 1TB drive then move to a larger disk - grow the partition, but on a kernel update it would no longer boot. This might have to do with the 2.19TB limitation of MBR - which means a move to GUID Partition Table (GPT) and possibly the need for a BIOS's that supports GUID. (See: http://en.wikipedia.org/wiki/GUID_Partition_Table ) In the mean time Debian installer fails to give any warning about larger drives and fdisk/sfdisk also fail to warn. The current kernels support GPT, but it is less than clear how older bios interact. It might be that just the boot disk needs to be smaller than 2.19TB and that storage disks formatted with GPT will work fine on machines with BIOS's that don't support GPT? It is also possible that fdisk/cfdisk/sfdisk are failing without warning if one tries to use these large drives. gparted supports EFI/GPT. I'm thinking that D-i needs to detect the large drive size, possible the ability of the bios to work with this drive size and give a warning. There might be problems supporting 2TB drives with the partioner in D-I that is independent to the BIOS. Sadly I have more questions than answers and hope someone with a better understanding of this issue writes it up. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110920010828.31805.60339.reportbug@malaysia.xtronics.network
Bug#545923: Tyan S7002
Package: installation-reports Boot method: CD Image version: debian-503-amd64-netinst.iso Date: Aug 31 2009 Machine: Tyan S7002 Processor: see attached cpuinfo Memory: see attached proc_meminfo Partitions: see atached last_300lines_of_partman Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[o] Configure network: [o] Detect CD: [o] Load installer modules: [o] Detect hard drives: [o] Partition hard drives: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Possibly connected with bug#508408 This box has 2 hitachi drives - set up two raid partitions each - one for swap the rest for root. Set the root partition to jfs and the other to swap finished with out much difficulty - but then: The kernel was unable to re-read the partition table on /dev/md1 (Invalid argument). This means Linux won't know anything about the modifications you made until you reboot. You should reboot your computer before doing anything with /dev/md1. Dropping down to the shell I see the raid building.. Waited for it to finish and restarted the install, but problem persists. I've attached information - let me know if more info is needed. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The best way to cheer yourself up is to try to cheer somebody else up. -- Mark twain processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping: 5 cpu MHz : 2000.069 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 sse4_2 popcnt lahf_lm bogomips: 4003.41 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping: 5 cpu MHz : 2000.069 cache size : 4096 KB physical id : 1 siblings: 4 core id : 0 cpu cores : 4 apicid : 16 initial apicid : 16 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 sse4_2 popcnt lahf_lm bogomips: 4000.06 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping: 5 cpu MHz : 2000.069 cache size : 4096 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 4 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca sse4_1 sse4_2 popcnt lahf_lm bogomips: 4000.05 clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 26 model name : Intel(R) Xeon(R) CPU E5504 @ 2.00GHz stepping: 5 cpu MHz : 2000.069 cache size : 4096 KB physical id : 1 siblings: 4 core id : 1 cpu cores : 4 apicid : 18 initial apicid : 18 fpu : yes fpu_exception : yes cpuid level : 11 wp
Bug#545923: Tyan S7002
I have the same exact problem on a second box - doubtful if it is hardware. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Post-modernism is a philosophy whose true message says Science is so hard, lets not even try to do it anymore.. And they don't. -kps -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544493: Should be fixed in new kernel
I'm wondering if there is an update for the installer with the fixed kernel 2.6.26-18? Is there a way to slide a different kernel into the install process? homas Goirand wrote 9/01/2009: Hi, I was wondering about the status of this patch. Will it be included in the next Lenny ? Note that we are currently maintaining a patched version of the Debian kernel on our repository, we are using the patched version on all our servers for months now, and we have noticed no regressions. It would be great if the decision to include them was taken, as it's a pain to have to patch, and compile, each time there's a security issue that triggers an upgrade. These were applied in kernel version 2.6.26-18 and will be in the next stable update (5.0.3) which should be released about a week from now. Ben. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The music is the real star; not the musician. kps -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544493: Tyan S7002 fails to detect network chips??
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/debian-cd/5.0.2a/amd64/iso-cd/debian-502a-amd64-netinst.iso Date: Aug 31 2009 Machine: Tyan S7002 Processor: Memory: Partitions: na Output of lspci -knn (or lspci -nn): Copied lines by hand: 0200.0 Ethernet controller intel corporation 82574L gigabit network connection [8086:10D3] 0300.0 Ethernet controller intel corporation 82574L gigabit network connection [8086:10D3] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [o] Detect network card:[E] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I checked and the e1000e driver exists. Tried several things with the BIOS - updated BIOS to latest version (1.03) NICs are enabled. Plugging live network cable in - causes lights to light - after very small delay. Google led me to this: http://lists.debian.org/debian-kernel/2009/06/msg00305.html Is there someplace I can get an updated driver? Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The best way to cheer yourself up is to try to cheer somebody else up. -- Mark twain -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#428906: instalation-report: Won't allow me to create root partition as jfs
Please close this bug - It was due to a not formatted partition. Might be a usability issue of the installer - should have warned me I was being stupid. What I did - I was installing over an old Linux drive. I removed all partitions, and recreated them - but I failed to mark them to be formatted. Geert Stappers wrote: Op 14-06-2007 om 20:59 schreef Karl Schmidt: -- System Information: Debian Release: 4.0r0 On a K7 system I was not able to have / as jfs. I have been able to do this befor and have other machines runnig that way. The install fails by saying it can not mount the / partition. To my mind comes to idea to load jfs kernel module. It is because I think that jfs.ko is not load by default by the installer. My advice is to play with the menu option load extra modules Hope this helps GSt -- !!! INCLUDE ALL TEXT IN TECHNICAL SUPPORT EMAIL REPLIES!!! !!!Send in plain-text mode - mail with attached GIFs will be rejected !!! Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 What happens if one get scared half to death twice? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428906: instalation-report: Won't allow me to create root partition as jfs
Package: instalation-report Version: debian-40r0-i386-netinst.iso Severity: important -- System Information: Debian Release: 4.0 On a K7 system I was not able to have / as jfs. I have been able to do this befor and have other machines runnig that way. The install fails by saying it can not mount the / partition. I reall don't want to use ext3... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
For people wanting to install Sarge on AMD64 I recommend using the mini.iso found here: http://amd64.debian.net/debian-installer/daily/netboot/ I did a sarge jfs on RAID with home on jfs/raid1/lvm with only minor problems with this iso. There should be a mention of this iso on the main installer page for the time being. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Time wounds all heels -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: versions of debian-installer
Geert Stappers wrote: On Thu, May 18, 2006 at 11:42:06AM -0500, Karl Schmidt wrote: I renamed this iso to debian-testing-amd64-netinst-5-13-06.iso Why not use such a naming system so people can see which build the iso was based on? The full URL contains the build date. Not really - http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Is there a better place to get pure amd64? How valuable are install bug reports if there is no reference to which install was run? The installed system and the ramdisk during install contains the file /etc/lsb-release which has build date. That says 20060408 -- but that is a lie - the files in the base directory of the iso have the more recent date I'm referring to. These are the daily built images. I'm still dead in the water - I even tried installing unbuntu and tried to move the install to testing - ubuntu worked, (had a 2.6.12 kernel) but trying to move to a pure Debian system turned into a total disaster. If I could get an install to go far enough that I can install a more recent kernel I think it would work. It might be that I need to go with a different kernel image - the generic instead of the K8? I renamed this iso to debian-testing-amd64-netinst-5-13-06.iso I doubt there is may 15th 2006 build of amd64. Please prove me wrong by booting with that ISO-image, switch to the second virtual console (by ALT-F2) and type `cat /etc/lsb-release` to get the actual build date. You can do that with any harm to the installed system (no need to re-install) Something is very wrong with that date - did they back up to an older version with older bugs? Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Why are so many spending time watching dark movies about hopelessness, the macabre, and perversion; why are they reading books about unfaithfulness and self destruction? Why is nothing uplifting, also considered 'cool' or entertaining? -kps -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367402: Tyan S2865
Tried the debian-testing-amd64-netinst.iso from the may 17th build. It fails at install base system - with DeBootstrap error - failed to determine codename for release. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Misdirection is the key to being a good magician. Magicians tell you they are doing something while they do something quite different; much like politicians -- except we can afford magicians. -KPS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366177: [amd64] Tyan S2877 installation-report
I noticed it - turned out /proc was not created. It is fixed in the version with dates of May 13, 06 (I renamed this iso to debian-testing-amd64-netinst-5-13-06.iso Why not use such a naming system so people can see which build the iso was based on? How valuable are install bug reports if there is no reference to which install was run?) What isn't fixed is the same problem as is in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367402 I need to find a way to run tests on the drive interface while booted from the install CDROM to isolate the problem. Filip Van Raemdonck wrote: Hi all, On Mon, May 08, 2006 at 01:50:41PM +0200, Geert Stappers wrote: On Sun, May 07, 2006 at 01:08:59PM -0500, Karl Schmidt wrote: May 8 01:59:22 debootstrap: dpkg-deb (subprocess): failed to exec tar: No such file or directory May 8 01:59:22 debootstrap: dpkg-deb: subprocess tar returned error exit status 2 I find it peculiar that no-one in this thread seemed to notice this error. I ran into the same issue, both with 15 may and 17 may netinst isos on amd64, on a supermicro (no nvidia hardware or anything evil involved) dual-opteron motherboard, with a single CPU installed. May 8 01:59:22 debootstrap: dpkg: error processing var/cache/apt/archives/base-passwd_3.5.11_amd64.deb (--install): May 8 01:59:22 debootstrap: subprocess dpkg-deb --control returned error exit status 2 May 8 01:59:22 debootstrap: Errors were encountered while processing: May 8 01:59:22 debootstrap: var/cache/apt/archives/base-passwd_3.5.11_amd64.deb It seems to be a reincarnation of #355379. That one was closed stating 'it should be fixed now' but with no reference as to which change supposedly fixed it. Frans? Regards, Filip -- !!! INCLUDE ALL TEXT IN TECHNICAL SUPPORT EMAIL REPLIES!!! Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Any cat would tell you that you can only wash one paw at a time; while we try to do everything at once. -kps -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366177: [amd64] Tyan S2877 installation-report
Karl Schmidt wrote: I noticed it - turned out /proc was not created. It is fixed in the version with dates of May 13, 06 I take that back - it is fixed if you chose a stable install, if you choose testing it fails. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The whole point of this sentence is to make clear what the whole point of this sentence is. --Douglas R. Hofstadter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367402: software raid jfs
using the debian-testing-amd64-netinst.iso from may 13 Wiped disk and tried this one again - Dropped down into shell just before the grub install and chroot /target added backports to sources.list apt-get update apt-get install linux-image-2.6.15-1-amd64-k8 complained about hotplug - and removed it?? went back and did the rest of the install. rebooted and things seemed to work, but no network wanted to install 2.6.16, but then it wouldn't let me log in - as if there was no root user? Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Any cat would tell you that you can only wash one paw at a time; while we try to do everything at once. -kps -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367402: Tyan S2865
Frans Pop wrote: On Monday 15 May 2006 19:45, Karl Schmidt wrote: Initial boot worked:[E] [...] Reboot: [E] Why did you put Error everywhere? Most of the installation must have gone OK looking at your comments below. Sorry - lack of sleep - I tried 6 different install CDs before I got this far... All the E's should be O's Comments/Problems: I did a sarge install on jfs on software RAID1. This had not worked on earlier versions of the installer. What do you mean exactly? Did jfs on RAID work with the Sarge installer or did it not? If not, _what_ did not work. Will run memtest and try to zero the supper blocks and start over. Sounds like a good option. If that fails too, could you please also try with ext3? That will help narrow it down to either the RAID setup of the jfs filesystem. My latest hunch is the nForce4 Ultra chip set - I'm trying to find a later kernel complied for Sarge that might have it fixed - no luck finding one I can wget from the install shell. I have talked to others that are running AMD64 with RAID or JFS without any problems. I think the highest probability is the nForce4 drivers. Could be some glitch in the SATA drivers? memtest86+ has been running non stop with restricted air flow for 6 hours now. I'm going to zero the super blocks on those drives and try again - make sure I created everything cleanly. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Merchandise offered without price, is sure to cost more than it is worth. -kps -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366177: [amd64] Tyan S2877 installation-report
Geert Stappers wrote: Retitle 366177 [amd64] Tyan S2877 installation-report Tags 366177 moreinfo Stop OK, I tried this install on a second motherboard - a Tyan S2865 and the missing /proc and the bass-psswd failed the same. I tried to install without any raid - same problem. This board has a different chip set: • nVIDIA nForce4 core-logic; SMSC DME1737 I wonder if this is a problem with the current install?? I see that others have installed on the S2865 in the past?? I also see that ubununtu works with it. -- Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 It looks like both parties are now playing the tax Peter to buy Paul's vote game. This won't end well. -kps
Bug#366177: [amd64] Tyan S2877 installation-report
Geert Stappers wrote: On Sun, May 07, 2006 at 01:08:59PM -0500, Karl Schmidt wrote: really bigsnip/ Next error: On installation of base system it would complain that there was no /proc - I created one by hand and that error went away. Hmm, that could be a not yet reported AMD64 thingy ... Next error: It would fail at installing base-passwd - complains about missing file or directory during a tar. I checked and all the mount points were there and all the directories used exist?? This one Is the show stopper for me - any hints?? Provide more information, like the name of the file that is missing. I got past this - creating the /target/proc and rerunning the 'install base system' caused a second error Could be this is from running 'install base system' twice? - but if I selected stable and dropped down to shell and chroot /target mkdir /proc = while 'install base system' was running == and did this as soon as the commands were available and before the error occurred. I got past the 'install base system' and to the install kernel part. This /proc problem exists on both a S2877 and S2865 motherboard - I also saw it mentioned on debian-amd64@lists.debian.org ,.,., But still no joy - it couldn't properly install a smd kernel on raid - so it is unbootable. (these should be Sarge kernels, but I don't see Sarge in the names on the list of offered kernels??) Today, I'm going to start over again and skip the RAID for now (I will use the page I wrote here to move back to raid later - see : http://xtronics.com/reference/SATA-RAID-debian-for-2.6.html ) I am now working with an installation image with root directory dates of May 6th. (I now loop mount these isos to find the dates and add a date string to the end of the iso file name - how do you guys make use of reports without knowing the build version of the package??) I also found that there may be an issue about initrd and a change in the name of kernel-image to linux-image - is there a particular kernel I should try to install for sarge? big snip Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 When everything is coming my way, I'm probably in the wrong lane. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366177: Tyan S2877 installation-report
I put in an older IDE drive for now. (note not a problem in Knoppix 4.0) I was setting up a RAID system - on retries it failed to see the raids?? I would then go to create the raid and it would say there were no partitions available send me back to the main partition menu and the raids would be there but would need to be reconfigured. I turned the BIOS raid off and wanted to use md software raid - many reasons to do this. Next error: On installation of base system it would complain that there was no /proc - I created one by hand and that error went away. Next error: It would fail at installing base-passwd - complains about missing file or directory during a tar. I checked and all the mount points were there and all the directories used exist?? This one Is the show stopper for me - any hints?? Next error: Would not create a /dev/sdxx for a usb drive I was going to use to transfer error logs from. I used ssh instead. Comment: IMHO it would seem like a good idea to have a build version in the name of the ISO. A Install report script might also be a good idea. If I can be of help with further testing let me know - I don't have this one up and running yet. Karl Schmidt EMail [EMAIL PROTECTED] Transtronics, Inc. WEB http://xtronics.com 3209 West 9th StreetPh (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Depression is merely anger without enthusiasm. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248567: Install for SATA RAID
Do you have some time to do another test of the image at http://gluck.debian.org/cdimage/testing/sarge_d-i/ and tell us how well it works? Were currently preparing or a new release and getting some feedback now would be appreciated. This install has gotten pushed back (a week?)- someone wants me to put it on an Opteron - instead of an asus A7V600 sata_via? I'm trying to get something with SATA and gigabit lan that isn't PCI bus limited. Any input on Opteron or SATA with Gilgabit lan mb would be welcome - I think it may not be supported in Debian testing at this time? I will contact you and get the latest sarge install a day or two ahead when I am ready. -- Karl Schmidt EMail[EMAIL PROTECTED] Transtronics, Inc.WEB http://xtronics.com 3209 West 9th Street Ph(785) 841-3089 Lawrence, KS 66049FAX(785) 841-0434 Everyone has a photographic memory, some just don't have film. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248567: Install for SATA RAID
I am not able to recreate what went wrong at this time - I will be doing a similar install in the next weeks and will take careful notes. Please close this bug for now. -- Karl Schmidt EMail[EMAIL PROTECTED] Transtronics, Inc.WEB http://xtronics.com 3209 West 9th Street Ph(785) 841-3089 Lawrence, KS 66049FAX(785) 841-0434 42.7% of all statistics are made up on the spot. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248567: Install for SATA RAID
Martin Michlmayr wrote: * Karl Schmidt [EMAIL PROTECTED] [2004-05-11 23:57]: There was a problem converting this systme to RAID. /lib/modules/2.4.25kps2/kernel/drivers/md did not contain raid1.o !! What is kps2? This does not look like a kernel Debian distributes. Debian kernels should certainly have raid1.o the module. Really need RAID install support with LVM Software RAID support will be in beta5. You can also try our daily snapshots. That should have read 2.4.25 -- the kps2 was a kernel I built attempting to fix the problem. You can verify the missing driver by looking in /lib/modules/2.4.25kps2/kernel/drivers/md in any install accomplished with intinstall Beta4 According to Herbert: Yes that's a good idea [checking for the existence of the module]. In fact it already does that for 2.6 kernels. For 2.4, because the support from modutils isn't as good, I've decided not to do it. -- Karl Schmidt EMail[EMAIL PROTECTED] Transtronics, Inc.WEB http://xtronics.com 3209 West 9th Street Ph(785) 841-3089 Lawrence, KS 66049FAX(785) 841-0434 He's about two bubbles off plumb. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248567: Install for SATA RAID
Package: installation-reports Debian-installer-version: 5/11/04 debian.org uname -a: Linux malaysia 2.4.26kps #1 SMP Sun May 2 17:40:22 CDT 2004 i686 GNU/Linux !! now installs 2.4.25 orig Date: 5/5/04 Method: CD boot network via DSL, not Proxied Machine: Intel D865PERL sith SATA drives Processor: P4 Memory: 512MB Root Device: IDE SATA originally HDE3 now MD2 Root Size/partition table: See http://xtronics.com/reference/SATA-RAID-Debian.htm Output of lspci: :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02) :00:03.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to CSA Bridge (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2) :02:01.0 Ethernet controller: Intel Corp. 82547EI Gigabit Ethernet Controller (LOM) :03:07.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 61) Base System Installation Checklist: Initial boot worked:[O ] Configure network HW: [O ] Config network: [O ] Detect CD: [O ] Load installer modules: [O ] Detect hard drives: [O ] Partition hard drives: [O ] Create file systems:[O ] Mount partitions: [O ] Install base system:[O ] Install boot loader:[O ] Reboot: [O ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: There was a problem converting this systme to RAID. /lib/modules/2.4.25kps2/kernel/drivers/md did not contain raid1.o !! rebooting degraded raid on /dev/md2 would fail with out giving clues - much time to figure this one out. mkinitrd did not report error and only when I updated to 2.4.26 did I get the needed driver. Really need RAID install support with LVM -- Karl Schmidt EMail[EMAIL PROTECTED] Transtronics, Inc.WEB http://xtronics.com 3209 West 9th Street Ph(785) 841-3089 Lawrence, KS 66049FAX(785) 841-0434 He's about a quarter turn past hand tight. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
