Re: SATA drives not recognized on new install
On Monday 30 April 2007 19:29, Lennart Sorensen wrote: On Sun, Apr 29, 2007 at 01:14:10AM -0700, Kenward Vaughan wrote: Thanks to you and Storm66 for your replies. I just burned and tried Ubuntu, Mepis, and Gentoo, and they all seemed to have no problems. The working kernel for the debian install was a 2.6.20. Is the sarge image based on 2.6.20 as well? You should be able to boot up with the Gentoo liveCD and use that to start the Debian installation manually -- from what I remember of my brief bout of infidelity, I don't think it needs the CD drive once it has booted. (If it does, try the Ubuntu or Mepis CDs; both of which are Debian underneath). Make sure your internet is working, though. Before the mid-install reboot, you will need to download and build an up-to-date kernel. (Or you could cheat and just copy the kernel from the boot CD; but you'd do best to build your own as soon as possible afterward.) -- AJS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
On Mon, Apr 30, 2007 at 05:27:44PM -0700, Kenward Vaughan wrote: Isn't it possible to create one on a usb drive, or from a mount point from which an ISO image can be generated? I was thinking of trying to roll my own kernel, then replace the kernel in the current setup. Or is this being naive?? It is a bit tricky, and involves generating udebs with kernel-wedge, and regenerating the debian-installer udebs based on that along with updating the package lists on the cd. I have done it, and it was a bit of a pain, but not too bad. Way way simpler than the old boot-floppies system of 3.0 and earlier. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Solved] Re: SATA drives not recognized on new install
On Sat, 2007-04-28 at 15:30 -0700, Kenward Vaughan wrote: Hi, I just built an amd box with a 5600+ processor on an MSI K9A Platinum MB. The latest (as of yesterday) netinst version of debian-amd64 was used to boot up the system. I saw none of the BIOS features which were mentioned on the installation page as things which had to be disabled, ran the memory up to 800 Mhz, etc., etc. The boot process times out when trying to communicate with the SATA drives (I have 2 WD drives, both recognized by Windows when I installed that later). The message given is along the lines of ata.1: SATA drive failed to IDENTIFY (I/O error errmask=0x104) ... Ah! What a delight! I retried this whole thing using the etch installer after seeing some information under a Google search for kernel support for the SB600 south bridge. (I was looking for help on setting up my own kernel's config.) Others have had similar problems as has been mentioned here, and a suggested workaround in one case included the boot parameters pci=nomsi irqpoll (which was a combo I had not tried). Worked like a charm for me as well. Etch was installed, which I changed to Sid (being slightly unstable myself :). I really appreciate the input I got from folks here. I have other questions, but those will come elsewhere. Cheers, Kenward -- With or without (religion) you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. --Physicist and Nobel Laureate Steven Weinberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
On Sun, Apr 29, 2007 at 01:14:10AM -0700, Kenward Vaughan wrote: Thanks to you and Storm66 for your replies. I just burned and tried Ubuntu, Mepis, and Gentoo, and they all seemed to have no problems. The working kernel for the debian install was a 2.6.20. Is the sarge image based on 2.6.20 as well? I'll check that link out too. Sarge is 2.6.8, etch is 2.6.18. http://kmuto.jp/debian/d-i/ has a 2.6.12 based sarge image which has helped many people in the past with installing sarge. Perhaps someone will make a 2.6.20 based etch installer similar to the sarge 2.6.12 installer to help out people who just have to have the latest and greatest in hardware. :) I did it before for sarge, so who knows maybe at some point I will feel like doing it again. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
On Sun, Apr 29, 2007 at 10:19:07AM +0200, michelcuppens wrote: I had the same problem with a MSI K9MM-V MoBo .I solved it by manually partitioning it, ie by determining the sizes and names myself (not using the proposed ones by the installer). Sata is treated as SCSI ,so the naming is sd(a...z)X Well, not quite. libata is treated as scsi and most sata drivers now use libata. Most PATA drivers are available as libata too in the recent 2.6 kernels. Basicaly in the future all harddrives will appear as scsi style disks. 2.4 had a number of SATA drivers that made /dev/hd* devices, but they quickly got replaced by libata which was a much better solution. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
On Mon, 2007-04-30 at 14:29 -0400, Lennart Sorensen wrote: On Sun, Apr 29, 2007 at 01:14:10AM -0700, Kenward Vaughan wrote: Thanks to you and Storm66 for your replies. I just burned and tried Ubuntu, Mepis, and Gentoo, and they all seemed to have no problems. The working kernel for the debian install was a 2.6.20. Is the sarge image based on 2.6.20 as well? I'll check that link out too. Sarge is 2.6.8, etch is 2.6.18. http://kmuto.jp/debian/d-i/ has a 2.6.12 based sarge image which has helped many people in the past with installing sarge. Perhaps someone will make a 2.6.20 based etch installer similar to the sarge 2.6.12 installer to help out people who just have to have the latest and greatest in hardware. :) I did it before for sarge, so who knows maybe at some point I will feel like doing it again. -- Len Sorensen Isn't it possible to create one on a usb drive, or from a mount point from which an ISO image can be generated? I was thinking of trying to roll my own kernel, then replace the kernel in the current setup. Or is this being naive?? Kenward -- With or without (religion) you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. --Physicist and Nobel Laureate Steven Weinberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
On Sat, 28 Apr 2007 15:30:55 -0700, Kenward Vaughan wrote Is this likely a problem of not having the right support built into the installation disk, and if so how can I get around that? I'm guessing your using the latest etch installer, which comes with a 2.6.18 kernel. You might want to try a debian installer with a more recent kernel. Perhaps something from here: http://kmuto.jp/debian/d-i/ Perhaps there is a custom etch installer out somewhere with 2.6.20 ? You could always install the sarge one from above and upgrade to etch afterwards. hth, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
Le samedi 28 avril 2007 à 15:30 -0700, Kenward Vaughan a écrit : Hi, I just built an amd box with a 5600+ processor on an MSI K9A Platinum MB. The latest (as of yesterday) netinst version of debian-amd64 was used to boot up the system. I saw none of the BIOS features which were mentioned on the installation page as things which had to be disabled, ran the memory up to 800 Mhz, etc., etc. Hello, I had the same problem with another MB. The problem seems to be related to the SB600 chip. The only method I found to cope with is to use a kernel with the SATA support totally disabled and putting the chip (BIOS) in Legacy IDE mode if your BIOS has such an option. I guess that the kernel 2.6.20 will work as some enhancements have been done in the kernel related to the SB600 chip. Another problem is that the SATA drives are not created whith /dev/hd... names but with /dev/sd If you can find an installer with a kernel 2.6.20 I think that you will have a full working system without any problem. Regards Storm66 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
On Sat, 2007-04-28 at 23:54 -0700, michael wrote: On Sat, 28 Apr 2007 15:30:55 -0700, Kenward Vaughan wrote Is this likely a problem of not having the right support built into the installation disk, and if so how can I get around that? I'm guessing your using the latest etch installer, which comes with a 2.6.18 kernel. You might want to try a debian installer with a more recent kernel. Perhaps something from here: http://kmuto.jp/debian/d-i/ Perhaps there is a custom etch installer out somewhere with 2.6.20 ? You could always install the sarge one from above and upgrade to etch afterwards. hth, Mike Thanks to you and Storm66 for your replies. I just burned and tried Ubuntu, Mepis, and Gentoo, and they all seemed to have no problems. The working kernel for the debian install was a 2.6.20. Is the sarge image based on 2.6.20 as well? I'll check that link out too. Kenward -- With or without (religion) you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. --Physicist and Nobel Laureate Steven Weinberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SATA drives not recognized on new install
Op zondag 29 april 2007 00:30, schreef Kenward Vaughan: Hi, I just built an amd box with a 5600+ processor on an MSI K9A Platinum MB. The latest (as of yesterday) netinst version of debian-amd64 was used to boot up the system. I saw none of the BIOS features which were mentioned on the installation page as things which had to be disabled, ran the memory up to 800 Mhz, etc., etc. The boot process times out when trying to communicate with the SATA drives (I have 2 WD drives, both recognized by Windows when I installed that later). The message given is along the lines of ata.1: SATA drive failed to IDENTIFY (I/O error errmask=0x104) Other lines earlier in the boot included SATA max udma/133 cmd 0xC200ED00 crt 0x0 bmda 0x0 irq 1277 and SATA link SStatus 123 SControl 300 (I have no clue whether these are helpful, though.) This happens for all 4 slots (with only 2 being populated, of course). I tried to get an idea of what people did with similar problems (amdforums), and tried a variety of boot options (noapic nolapic; noapic acpi=noirq|off ; etc.), none of which helped. One time I was able to shft-pgup and saw a line about a BIOS bug, along with the letters MCFG, but I couldn't catch it again at other times. Looking at dmesg later on following a normal boot showed no such line in the part of dmesg which had been saved. It appears that most if not all other HW is recognized, including the LAN. The K9A has the ATI RD580 north bridge chip and SB600 south bridge, and is a Crossfire board (which I don't care about). The BIOS version is 1.3 (Dec. '06). Is this likely a problem of not having the right support built into the installation disk, and if so how can I get around that? Can I build an amd64 kernel on my 32 bit kernel machine and somehow build a bootable disk off of that? (a flash drive perhaps?) Many thanks for any help! Kenward -- With or without (religion) you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. --Physicist and Nobel Laureate Steven Weinberg I had the same problem with a MSI K9MM-V MoBo .I solved it by manually partitioning it, ie by determining the sizes and names myself (not using the proposed ones by the installer). Sata is treated as SCSI ,so the naming is sd(a...z)X Hope it can help you. Michel Cuppens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SATA drives not recognized on new install
Hi, I just built an amd box with a 5600+ processor on an MSI K9A Platinum MB. The latest (as of yesterday) netinst version of debian-amd64 was used to boot up the system. I saw none of the BIOS features which were mentioned on the installation page as things which had to be disabled, ran the memory up to 800 Mhz, etc., etc. The boot process times out when trying to communicate with the SATA drives (I have 2 WD drives, both recognized by Windows when I installed that later). The message given is along the lines of ata.1: SATA drive failed to IDENTIFY (I/O error errmask=0x104) Other lines earlier in the boot included SATA max udma/133 cmd 0xC200ED00 crt 0x0 bmda 0x0 irq 1277 and SATA link SStatus 123 SControl 300 (I have no clue whether these are helpful, though.) This happens for all 4 slots (with only 2 being populated, of course). I tried to get an idea of what people did with similar problems (amdforums), and tried a variety of boot options (noapic nolapic; noapic acpi=noirq|off ; etc.), none of which helped. One time I was able to shft-pgup and saw a line about a BIOS bug, along with the letters MCFG, but I couldn't catch it again at other times. Looking at dmesg later on following a normal boot showed no such line in the part of dmesg which had been saved. It appears that most if not all other HW is recognized, including the LAN. The K9A has the ATI RD580 north bridge chip and SB600 south bridge, and is a Crossfire board (which I don't care about). The BIOS version is 1.3 (Dec. '06). Is this likely a problem of not having the right support built into the installation disk, and if so how can I get around that? Can I build an amd64 kernel on my 32 bit kernel machine and somehow build a bootable disk off of that? (a flash drive perhaps?) Many thanks for any help! Kenward -- With or without (religion) you would have good people doing good things and evil people doing evil things. But for good people to do evil things, that takes religion. --Physicist and Nobel Laureate Steven Weinberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new install
Koen Op 16 juni is er klasbijeenkomst. Kan je komen. Wil je ook bij je antwoord als je adresgegevens opgeven tel el GSM? mvg Olivier Ruysschaert attachment: winmail.dat
Re: new install
[EMAIL PROTECTED] (Lennart Sorensen) writes: On Wed, Apr 19, 2006 at 10:51:26PM -0400, Anthony DeRobertis wrote: That really shouldn't matter. The RAID superblocks for all RAID levels contain a UUID for a reason. With DEVICE partitions in /etc/mdadm/mdadm.conf, mdadm will check /proc/partitions for all partitions and scan each for your raid disks. [Not sure how to make mkinitramfs do this, though.] The problem I get is that on some boots I get: piix: sdc, sdd /dev/md0 = /dev/sda1+/dev/sdb1 (boot) /dev/md1 = /dev/sda2+/dev/sdb2 (root) /dev/md2 = /dev/sda3+/dev/sdb3 (lvm first PV) promise: sda, sdb /dev/md3 = /dev/sdc1+/dev/sdd1 (lvm second PV) and on others I get: promise: sda, sdb /dev/md0 = /dev/sda1+/dev/sdb1 (lvm second PV) piix: sdc, sdd /dev/md1 = /dev/sdc1+/dev/sdd1 (boot) /dev/md2 = /dev/sdc2+/dev/sdd2 (root) /dev/md3 = /dev/sdc3+/dev/sdd3 (lvm first PV) So now, do I pass root=/dev/md1 or root=/dev/md2? Seems 50% of the time it is one, and 50% of the time the other. Bloody pain really. I tried passing root=LABEL=ROOT but for some reason, at least with 2.6.15, /dev/disk/ needed to access by label doesn't exist so at least with the way initramfs-tools makes the initrd, it can't find root that way. So my raid componets always start up just fine, the problem is knowing which raid md device is the right one to mount as root. Len Sorensen Check your initramfs. I guess that one screws it up, probably together with udev. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new install
On Wed, Apr 19, 2006 at 10:51:26PM -0400, Anthony DeRobertis wrote: That really shouldn't matter. The RAID superblocks for all RAID levels contain a UUID for a reason. With DEVICE partitions in /etc/mdadm/mdadm.conf, mdadm will check /proc/partitions for all partitions and scan each for your raid disks. [Not sure how to make mkinitramfs do this, though.] The problem I get is that on some boots I get: piix: sdc, sdd /dev/md0 = /dev/sda1+/dev/sdb1 (boot) /dev/md1 = /dev/sda2+/dev/sdb2 (root) /dev/md2 = /dev/sda3+/dev/sdb3 (lvm first PV) promise: sda, sdb /dev/md3 = /dev/sdc1+/dev/sdd1 (lvm second PV) and on others I get: promise: sda, sdb /dev/md0 = /dev/sda1+/dev/sdb1 (lvm second PV) piix: sdc, sdd /dev/md1 = /dev/sdc1+/dev/sdd1 (boot) /dev/md2 = /dev/sdc2+/dev/sdd2 (root) /dev/md3 = /dev/sdc3+/dev/sdd3 (lvm first PV) So now, do I pass root=/dev/md1 or root=/dev/md2? Seems 50% of the time it is one, and 50% of the time the other. Bloody pain really. I tried passing root=LABEL=ROOT but for some reason, at least with 2.6.15, /dev/disk/ needed to access by label doesn't exist so at least with the way initramfs-tools makes the initrd, it can't find root that way. So my raid componets always start up just fine, the problem is knowing which raid md device is the right one to mount as root. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new install
On Tue, Apr 18, 2006 at 09:56:08AM -0400, Lennart Sorensen wrote: Of course if your raid consists of drives from all of them, it probably won't be a problem. My problem is I have a raid1 on each controller, and the order of my raid devices gets rearranged when the controllers load in reverse order. That really shouldn't matter. The RAID superblocks for all RAID levels contain a UUID for a reason. With DEVICE partitions in /etc/mdadm/mdadm.conf, mdadm will check /proc/partitions for all partitions and scan each for your raid disks. [Not sure how to make mkinitramfs do this, though.] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
new install
Hi, I'm going to perform a new install on an Asus motherboard with the following sata controllers: :00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02) :00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) I have 4 250GB SATA drives which I would like to use in (software) RAID5 with LVM on top. I would love to use one of the newer kernels (2.6.15) but earlier comments from Lennart Sorensen about sata drives not always being recognised in the same order with this particular kernel has frightend me a bit. Does this mean that the raid won't assemble properly and I won't be able to boot? On that note, is it better to still have a small unraided /boot partition to help grub rather than put everything on RAID5? Thanks in advance, Koen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new install
On Tue, Apr 18, 2006 at 02:24:43PM +0100, Koen Tavernier wrote: I'm going to perform a new install on an Asus motherboard with the following sata controllers: :00:08.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02) :00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) I have 4 250GB SATA drives which I would like to use in (software) RAID5 with LVM on top. I would love to use one of the newer kernels (2.6.15) but earlier comments from Lennart Sorensen about sata drives not always being recognised in the same order with this particular kernel has frightend me a bit. Does this mean that the raid won't assemble properly and I won't be able to boot? Right now, the system which I have with an intel and a promise sata controller manages to boot 50% of the time. If it fails, I reboot and it usually works. It really seems to decide to load the sata drivers randomly (or more like it loads them both at the same time, and sometimes one finishes loading first, sometimes the other). initramfs-tools really needs somewhere I can specify to load certain modules first before letting udev at things. I haven't found such a place yet, although I haven't looked very hard either. Of course if your raid consists of drives from all of them, it probably won't be a problem. My problem is I have a raid1 on each controller, and the order of my raid devices gets rearranged when the controllers load in reverse order. raid5 should probably figure it out just fine no matter what order they are in. On that note, is it better to still have a small unraided /boot partition to help grub rather than put everything on RAID5? grub can NOT read raid5. Only raid1. So you don't have a choice. A small raid1 partition is nice to have for grub. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Russ Cook [EMAIL PROTECTED] écrit : Thank you both for your helpful suggestions. Now that sound is working, I can turn to other problems - like whether to install a 32-bit chroot for programs like Mplayer, Mozilla with Java support, etc. If you want to get a 64 bit mplayer version, you can add the following line to your source.list deb http://spello.sscnet.ucla.edu/marillat/ sid main Philippe -- [EMAIL PROTECTED] http://photos.arnone.org/ signature.asc Description: Digital signature
Re: New install - no sound
On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Use gstreamer-properties to make gstreamer use alsa. Russ Cook wrote: Partial success. After installing the programs I could find from the referenced list, XMMS now works. Rythmbox 0.8.8 still fails with the error message 'Could not create audio output element; check your setting'. Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just be root. adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- Matthew A. Nicholson Digium -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Oops. I reran alsaconf. That killed a process that was running (I don't know what it was). Afterwards, both XMMS and Rythmbox are functional now. Thank you both for your helpful suggestions. Now that sound is working, I can turn to other problems - like whether to install a 32-bit chroot for programs like Mplayer, Mozilla with Java support, etc. Thanks again. I really appreciate your help. Regards, Russ Russ Cook wrote: Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Kernels 2.6.12 enable something called dmix by default if your soundcard does not support multiple channels. This would allow rhythmbox and xmms to play sounds at the same time without esd/alsa/your sound server. This is a very cool feature that I sorely missed for a long time. Russ Cook wrote: Oops. I reran alsaconf. That killed a process that was running (I don't know what it was). Afterwards, both XMMS and Rythmbox are functional now. Thank you both for your helpful suggestions. Now that sound is working, I can turn to other problems - like whether to install a 32-bit chroot for programs like Mplayer, Mozilla with Java support, etc. Thanks again. I really appreciate your help. Regards, Russ Russ Cook wrote: Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- Matthew A. Nicholson Digium -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
On Sun, Dec 11, 2005 at 08:53:09AM -0200, Eduardo M KALINOWSKI wrote: Russ Cook wrote: I have an ASUS A8N32 SLI Deluxe motherboard with an AMD4800 dual core processor. I believe the audio is Realtek ALC850. I performed a clean install from unstable from http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main. My system is up and running, and I have been performing apt-get update and upgrade periodically. My kernel is vmlinuz-2.6.12-1-amd64-k8-smp. My problem is that I don't have any sound from the system. Attached is the output from 'lsmod'. The utility 'Discover' is installed. Can anyone offer some pointers? This will seem weird, but try plugging your speakers in another jack - the microphone or the line out one. I have a similar board, and sound is output through the microphone jack, not the speaker jack. I still don't know why. Because intel and others @[EMAIL PROTECTED] with the AC97 standard. The snd-intel8x0 driver has a quirks option that allows for rearanging that stupidity back to normal. parm: ac97_quirk:AC'97 workaround for strange hardware. (array of charp) You might have to look at pci/ac97/ac97_codec.c for a list of valid quirk options. For a realtek ALC chip the option ac97_quirk=alc_jack might be useful (it appears to enable the auto jack select feature of those chips). There are also quirks for swapping master/headphone volume controls which seems to be needed on some systems. AC97 is a real mess. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just be root. adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Partial success. After installing the programs I could find from the referenced list, XMMS now works. Rythmbox 0.8.8 still fails with the error message 'Could not create audio output element; check your setting'. Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just be root. adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. Matthew A. Nicholson wrote: Install udev, modprobe snd_intel8x0, use alsamixer to adjust your volume, enjoy your sound. Simple. :) Russ Cook wrote: Thanks much for the reply. I did NOT have the alsa-utils installed. I thought I had, and that the system was configured. I have now installed alsa-utils, alsa-base, and alsa-oss, and run alsaconf. My modules and /dev do not match yours. You can tell by now that I am not expert at this. I will compile my own kernel once I get everything up and running, so I have a fall-back in case I incorrectly set some options for the custom kernel. Any further pointers would be greatly appreciated. Thanks again. Russ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
You didn't follow my directions... First make sure you are part of the audio group, you generally should just be root. adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message No volume control elements and/or devices found. When I try to play a file using Rythmbox 0.8.8, I get the message Could not create audio output element; check your settings.When I clicked on the volume monitor under the Sound and Video menu item of Gnome, I get the error message Cannot connect to sound daemon. Please run 'esd' at a command prompt. From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message Could not create audio output element; check your settings. This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- Matthew A. Nicholson Matt-Land.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New install - no sound
I have an ASUS A8N32 SLI Deluxe motherboard with an AMD4800 dual core processor. I believe the audio is Realtek ALC850. I performed a clean install from unstable from http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main. My system is up and running, and I have been performing apt-get update and upgrade periodically. My kernel is vmlinuz-2.6.12-1-amd64-k8-smp. My problem is that I don't have any sound from the system. Attached is the output from 'lsmod'. The utility 'Discover' is installed. Can anyone offer some pointers? Thanks much, Russ Module Size Used by md5 6720 1 ipv6 290144 10 thermal17228 0 fan 7304 0 button 9824 0 processor 26728 1 thermal ac 7624 0 battery12680 0 af_packet 29964 2 ide_scsi 21380 0 sd_mod 22016 0 sr_mod 20708 0 sbp2 28040 0 eth139423888 0 usb_storage80192 0 joydev 13568 0 snd_mpu401 10248 0 evdev 13120 0 snd_intel8x0 38784 0 snd_mpu401_uart10880 1 snd_mpu401 snd_ac97_codec 91588 1 snd_intel8x0 snd_rawmidi31776 1 snd_mpu401_uart snd_seq_device 11920 1 snd_rawmidi snd_pcm 106632 2 snd_intel8x0,snd_ac97_codec sata_nv12676 0 i2c_nforce210048 0 snd_timer 29256 1 snd_pcm ide_cd 46112 0 snd64800 8 snd_mpu401,snd_intel8x0,snd_mpu401_uart,snd_ac97_codec,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer libata 53128 1 sata_nv ehci_hcd 37704 0 i2c_core 26688 1 i2c_nforce2 psmouse31748 0 cdrom 41848 2 sr_mod,ide_cd ohci1394 38156 0 ieee1394 372152 3 sbp2,eth1394,ohci1394 parport_pc 41584 0 scsi_mod 156280 6 ide_scsi,sd_mod,sr_mod,sbp2,usb_storage,libata snd_page_alloc 13832 2 snd_intel8x0,snd_pcm forcedeth 23168 0 analog 13856 0 ohci_hcd 24644 0 soundcore 13600 1 snd serio_raw 10372 0 pcspkr 6296 0 parport44044 1 parport_pc gameport 19912 1 analog floppy 70056 0 rtc17160 0 ext3 142352 5 jbd66480 1 ext3 mbcache13768 1 ext3 ide_disk 20224 7 ide_generic 3584 0 [permanent] via82cxxx 15728 0 [permanent] trm290 6916 0 [permanent] triflex 6464 0 [permanent] slc90e668576 0 [permanent] sis551316980 0 [permanent] siimage14720 0 [permanent] serverworks11280 0 [permanent] sc1200 10176 0 [permanent] rz1000 5120 0 [permanent] piix 14020 0 [permanent] pdc202xx_old 14080 0 [permanent] opti621 7236 0 [permanent] ns87415 6892 0 [permanent] hpt366 22400 0 [permanent] hpt34x 7808 0 [permanent] generic 7168 0 [permanent] cy82c6937240 0 [permanent] cs5530 8512 0 [permanent] cs5520 7424 0 [permanent] cmd64x 14344 0 [permanent] atiixp 8720 0 [permanent] amd74xx17200 0 [permanent] alim15x3 14492 0 [permanent] aec62xx10368 0 [permanent] pdc202xx_new 12160 0 [permanent] ide_core 149688 30 ide_scsi,usb_storage,ide_cd,ide_disk,ide_generic,via82cxxx,trm290,triflex,slc90e66,sis5513,siimage,serverworks,sc1200,rz1000,piix,pdc202xx_old,opti621,ns87415,hpt366,hpt34x,generic,cy82c693,cs5530,cs5520,cmd64x,atiixp,amd74xx,alim15x3,aec62xx,pdc202xx_new unix 37016 385 fbcon 41088 0 tileblit4800 1 fbcon font 10880 1 fbcon bitblit 8128 1 fbcon vesafb 11240 0 cfbcopyarea 6144 1 vesafb cfbimgblt 5056 1 vesafb cfbfillrect 6784 1 vesafb softcursor 4736 1 vesafb
Re: New install - no sound
Thanks much for the reply. I did NOT have the alsa-utils installed. I thought I had, and that the system was configured. I have now installed alsa-utils, alsa-base, and alsa-oss, and run alsaconf. My modules and /dev do not match yours. You can tell by now that I am not expert at this. I will compile my own kernel once I get everything up and running, so I have a fall-back in case I incorrectly set some options for the custom kernel. Any further pointers would be greatly appreciated. Thanks again. Russ Michael Langley wrote: On Sat, 10 Dec 2005 17:11:23 -0600 Russ Cook [EMAIL PROTECTED] wrote: I have an ASUS A8N32 SLI Deluxe motherboard with an AMD4800 dual core processor. I believe the audio is Realtek ALC850. I performed a clean install from unstable from http://mirror.espri.arizona.edu/debian-amd64/debian/ testing main. My system is up and running, and I have been performing apt-get update and upgrade periodically. My kernel is vmlinuz-2.6.12-1-amd64-k8-smp. My problem is that I don't have any sound from the system. Attached is the output from 'lsmod'. The utility 'Discover' is installed. Can anyone offer some pointers? Thanks much, Russ I'm assuming you have alsaconf, alsamixer and alsactl installed (alsa-utils) and the proper devices in /dev to use your hardware. You might also want to install alsa-oss and alsa-base. I also have Realtek onboard audio with the ALC850 chip. I always build my own kernel and the latest version of alsa. I have alsa 1.0.10 installed with kernel 2.6.14.3 that I built myself. Below is the modules I am using for alsa. snd_seq_oss38436 0 snd_seq_midi 10240 0 snd_rawmidi30752 1 snd_seq_midi snd_seq_midi_event 9152 2 snd_seq_oss,snd_seq_midi snd_seq61400 5 snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_seq_device 10192 4 snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd_intel8x0 37096 0 snd_ac97_codec108220 1 snd_intel8x0 snd_ac97_bus2880 1 snd_ac97_codec snd_pcm_oss58400 0 snd_mixer_oss 19584 1 snd_pcm_oss snd_pcm 104012 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 28040 2 snd_seq,snd_pcm snd68096 10 snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer snd_page_alloc 12112 2 snd_intel8x0,snd_pcm soundcore 12320 1 snd This is what my /dev looks like. 0 lrwxrwxrwx 1 root root 5 Nov 25 21:17 /dev/adsp - adsp0 0 crw-rw 1 root audio 14, 12 Nov 25 21:17 /dev/adsp0 0 crw-rw 1 root audio 14, 28 Nov 25 21:17 /dev/adsp1 0 crw-rw 1 root audio 14, 44 Nov 25 21:17 /dev/adsp2 0 crw-rw 1 root audio 14, 60 Nov 25 21:17 /dev/adsp3 0 lrwxrwxrwx 1 root root 4 Nov 25 21:17 /dev/dsp - dsp0 0 crw-rw-rw- 1 root audio 14, 3 Nov 25 21:17 /dev/dsp0 0 crw-rw-rw- 1 root audio 14, 19 Nov 25 21:17 /dev/dsp1 0 crw-rw-rw- 1 root audio 14, 35 Nov 25 21:17 /dev/dsp2 0 crw-rw-rw- 1 root audio 14, 51 Nov 25 21:17 /dev/dsp3 You might try running alsaconf to detect your card or alsamixer to make sure your levels aren't all the way down. Other than that I don't know what to tell you. But the ALC850 chip definitely works with alsa. From alsamixer: Card: ALi M5455 Chip: Realtek ALC850 rev 0 snd_intel8x0 38784 0 snd_ac97_codec 91588 1 snd_intel8x0 snd_pcm_oss59360 0 snd_mixer_oss 21120 1 snd_pcm_oss snd_pcm 106632 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 29256 1 snd_pcm snd64800 6 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 13600 1 snd snd_page_alloc 13832 2 snd_intel8x0,snd_pcm crw-rw 1 root audio 14, 12 2005-12-10 18:41 /dev/adsp crw-rw 1 root audio 14, 4 2005-12-10 18:41 /dev/audio crw-rw 1 root audio 14, 3 2005-12-10 18:41 /dev/dsp
New Install works great! My experience.
I spend a lot of time trying to figure out if I should try 64bit. For those of you searching. I installed amd64 stable and upgraded to unstable. Everything works great! Good job to the AMD64 team! The only snag I hit was udev. udev wanted 2.6.12 or higher, though it didn't show up as a dependency. However I didn't have that, and didn't know until half gnome was installed. Not sure if there was a better way, but I just removed udev and all the broken packages it brought with it. Then put on the new 2.6.12 kernel and viola! the latest mkisofs also caused a seg fault. I moved to the version just prior to that and works fine. Epiphany works fine. Evolution, well I'm using it now. totem gstreamer plays mp3s, mpegs, dvd no prob. rt2500 works great. nforce4 and 6600gt work great. Nvidia driver install was a snap (built using deb packages) now I just need to get ut2004 working. MD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: complete new install
Am Freitag, den 18.03.2005, 08:10 +0100 schrieb Uwe: 2) I have trouble getting that cool'n'quiet thing running. As the powernow-daemon relies on the /sys-filesystem i suggest defaulting it in the kernel-images. I installed the sysfsutils package but can't get the /sys-filesystem working. Especially the cpu-freq part is not available. the sysfsutils-daemon fires up, but powernow doesn't. Hi for powernowd you have to load the module powernow_k8. I have loaded the module cpufrq_powersave too. And it works fine. -- Alexander Jede [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: complete new install
On Thursday 17 March 2005 09:17, Alexander wrote: Am Freitag, den 18.03.2005, 08:10 +0100 schrieb Uwe: 2) I have trouble getting that cool'n'quiet thing running. As the powernow-daemon relies on the /sys-filesystem i suggest defaulting it in the kernel-images. I installed the sysfsutils package but can't get the /sys-filesystem working. Especially the cpu-freq part is not available. the sysfsutils-daemon fires up, but powernow doesn't. Hi for powernowd you have to load the module powernow_k8. I have loaded the module cpufrq_powersave too. And it works fine. yes, that's it. thanks. -- --- ASUS K8S-MX, 2800+ (754), 512MB, gnuLinux v2.6.x -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
complete new install
Hi there, I'm new to this list and first of all want to thank everybody involved in the development of the AMD64 port. I upgraded my personal server from a double PII to a small Athlon64 system. First of all I'd like to suggest adding a new mainboard to the compatibility list. Attached you can find the necessary info. I tested everything but the sound an the SATA part with success. After installation out of the box via netinst-image I have some questions: 1) data-transfer from disk to disk seems to be very slo and cpu conduming. copying huge files from USB-disk to IDE-disk ist very very slow with a load of nearly 90%. It seems to be independent from the filesystemtype - it's the same for FAT32 and NTFS sources. 2) I have trouble getting that cool'n'quiet thing running. As the powernow-daemon relies on the /sys-filesystem i suggest defaulting it in the kernel-images. I installed the sysfsutils package but can't get the /sys-filesystem working. Especially the cpu-freq part is not available. the sysfsutils-daemon fires up, but powernow doesn't. ANY SUGGESTIONS? Greetings Uwe PS: Whenever you try to use a harddrive previously used in a Sun with a sundisklabel ERASE it completely. The netinst shows a very strange behaviour until you entirely scrubb your harddisk. I used the IBM Drive Fitness Test and did a complete erase... -- --- ASUS K8S-MX, 2800+ (754), 512MB, gnuLinux v2.6.x # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hda1 / ext3defaults,errors=remount-ro 0 1 /dev/hdc1 /datatwoext3defaults0 2 /dev/hda2 noneswapsw 0 0 #/dev/hdb/media/cdrom0 iso9660 ro,user,noauto 0 0 sysfs /sys sysfs defaults 0 0 #/dev/pktcdvd/0 /mnt/dvdram udf noauto,noatime,rw,users 0 0 /dev/hdb /mnt/dvdram udf noauto,noatime,rw,users 0 0 Bootdata ok (command line is root=/dev/hda1 ro ) Linux version 2.6.10-16032hz ([EMAIL PROTECTED]) (gcc-Version 3.3.5 (Debian 1:3.3.5-12)) #1 Thu Mar 17 17:10:01 CET 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 1dfd (usable) BIOS-e820: 1dfd - 1dfdf000 (ACPI data) BIOS-e820: 1dfdf000 - 1e00 (ACPI NVS) BIOS-e820: ff78 - 0001 (reserved) No mptable found. On node 0 totalpages: 122832 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 118736 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 ACPI: RSDP (v002 ACPIAM) @ 0x000fb120 ACPI: XSDT (v001 A M I OEMXSDT 0x11000411 MSFT 0x0097) @ 0x1dfd0100 ACPI: FADT (v003 A M I OEMFACP 0x11000411 MSFT 0x0097) @ 0x1dfd0290 ACPI: MADT (v001 A M I OEMAPIC 0x11000411 MSFT 0x0097) @ 0x1dfd0390 ACPI: OEMB (v001 A M I AMI_OEM 0x11000411 MSFT 0x0097) @ 0x1dfdf040 ACPI: DSDT (v001 AH005 AH005001 0x0001 INTL 0x02002026) @ 0x ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 16 ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 20, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Checking aperture... CPU 0: aperture @ e000 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) AGP bridge at 00:00:00 Aperture from AGP @ e000 size 32 MB (APSIZE f38) Aperture from AGP bridge too small (32 MB) Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Mapping aperture over 65536 KB of RAM @ 400 Built 1 zonelists Kernel command line: root=/dev/hda1 ro console=tty0 Initializing CPU#0 PID hash table entries: 2048 (order: 11, 65536 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1804.013 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) Memory: 411412k/491328k available (1670k kernel code, 79132k reserved, 964k data, 140k init) Calibrating delay loop... 3571.71 BogoMIPS (lpj=1785856) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 256 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: AMD
Re: X Strangeness with mouse after new install
See my answer for kdm and psaux post http://lists.debian.org/debian-amd64/2004/11/msg00181.html post -- Slava Risenberg tailgunn at netvision.net.il
Re: X Strangeness with mouse after new install
--- Bob Proulx [EMAIL PROTECTED] wrote: Artimus Dink wrote: (**) Option Device /dev/psaux (EE) xf86OpenSerial: Cannot open device /dev/psaux No such device. (EE) Configured Mouse: cannot open input device (EE) PreInit failed for input device Configured Mouse [...] (**) Option Device /dev/input/mice (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. Hmm... If I try 'startx' again, I get this... That seems really bizarre to me. I am sure most people are not seeing such strange stuff. someone suggested adding mousedev and pmouse to /etc/modules. If I do this, X starts on the first try, but the mouse doesn't work at all. That seems reasonable. I usually have those on woody machines. Sarge has both hotplug and discover and one of those loads those drivers for me at system boot time. I looked at /etc/X11/XF86Config-4 and found that I have entries for Configured Mouse at /dev/psaux and Generic Mouse at /dev/input/mice. This struck me as a bit odd, but I have an x86 machine running Debian Sarge... its XF86Config-4 is set up the same way and X has always worked flawlessly. That looks normal for me. That is how you can have both a (im)ps2 mouse and a usb mouse at the same time. Can someone tell me what's going on? I've run Fedora Not a clue. But is your mouse outputing information? Try this. When you move the mouse you should see some data from the device. Break out of it to stop it. sudo od -tx1 /dev/psaux If you have mousedev loaded then the /dev/input/mice should work too. sudo od -tx1 /dev/input/mice If you don't see anything then there is no way that X11 will see anything either. Bob ATTACHMENT part 2 application/pgp-signature name=signature.asc __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com
Re: X Strangeness with mouse after new install
Not a clue. But is your mouse outputing information? Try this. When you move the mouse you should see some data from the device. Break out of it to stop it. sudo od -tx1 /dev/psaux If you have mousedev loaded then the /dev/input/mice should work too. sudo od -tx1 /dev/input/mice If you don't see anything then there is no way that X11 will see anything either. Bob Sorry about the empty reply... caffiene is a bad idea this late in the evening... I definately get output from both sudo commands, and 'lsmod' confirms that the modules are loaded after I manage to get X up and working. Again, I tried adding psmouse and mousedev to /etc/modules, but in that case X starts but the mouse doesn't work at all. One thing I've found is that if I do a 'modprobe psmouse' prior to 'startx', then X will start straight away and the mouse works fine... any ideas? __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com
Re: X Strangeness with mouse after new install
Artimus Dink wrote: One thing I've found is that if I do a 'modprobe psmouse' prior to 'startx', then X will start straight away and the mouse works fine... any ideas? I am guessing that either hotplug or discover or something else is installed on my machine and loading that module automatically while on your machine it is not. Add psmouse to /etc/modules so that it is always loaded. This was always needed previously with woody. It is a tried and true method. Bob signature.asc Description: Digital signature
Re: X Strangeness with mouse after new install
Artimus Dink wrote: (**) Option Device /dev/psaux (EE) xf86OpenSerial: Cannot open device /dev/psaux No such device. (EE) Configured Mouse: cannot open input device (EE) PreInit failed for input device Configured Mouse [...] (**) Option Device /dev/input/mice (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. Hmm... If I try 'startx' again, I get this... That seems really bizarre to me. I am sure most people are not seeing such strange stuff. someone suggested adding mousedev and pmouse to /etc/modules. If I do this, X starts on the first try, but the mouse doesn't work at all. That seems reasonable. I usually have those on woody machines. Sarge has both hotplug and discover and one of those loads those drivers for me at system boot time. I looked at /etc/X11/XF86Config-4 and found that I have entries for Configured Mouse at /dev/psaux and Generic Mouse at /dev/input/mice. This struck me as a bit odd, but I have an x86 machine running Debian Sarge... its XF86Config-4 is set up the same way and X has always worked flawlessly. That looks normal for me. That is how you can have both a (im)ps2 mouse and a usb mouse at the same time. Can someone tell me what's going on? I've run Fedora Not a clue. But is your mouse outputing information? Try this. When you move the mouse you should see some data from the device. Break out of it to stop it. sudo od -tx1 /dev/psaux If you have mousedev loaded then the /dev/input/mice should work too. sudo od -tx1 /dev/input/mice If you don't see anything then there is no way that X11 will see anything either. Bob signature.asc Description: Digital signature
X Strangeness with mouse after new install
I have a fresh install of Debian amd64 / pure64. Most everything seems to work fine, but I have a hard time getting X started. Initially I disabled xdm, but it didn't help any. Basically, I'll type 'startx', wait a few seconds and x will fail. The last few lines of /var/log/XFree86.0.log read... (II) Keyboard Generic Keyboard handled by legacy driver (**) Option Protocol PS/2 (**) Configured Mouse: Protocol: PS/2 (**) Option CorePointer (**) Configured Mouse: Core Pointer (**) Option Device /dev/psaux (EE) xf86OpenSerial: Cannot open device /dev/psaux No such device. (EE) Configured Mouse: cannot open input device (EE) PreInit failed for input device Configured Mouse (II) UnloadModule: mouse (**) Option Protocol ImPS/2 (**) Generic Mouse: Protocol: ImPS/2 (**) Option SendCoreEvents true (**) Generic Mouse: always reports core events (**) Option Device /dev/input/mice (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device Generic Mouse (II) UnloadModule: mouse (WW) No core pointer registered No core pointer Fatal server error: failed to initialize core devices If I try 'startx' again, I get this... (II) Keyboard Generic Keyboard handled by legacy driver (**) Option Protocol PS/2 (**) Configured Mouse: Protocol: PS/2 (**) Option CorePointer (**) Configured Mouse: Core Pointer (**) Option Device /dev/psaux (**) Option Emulate3Buttons true (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 (**) Configured Mouse: Buttons: 5 (**) Option Protocol ImPS/2 (**) Generic Mouse: Protocol: ImPS/2 (**) Option SendCoreEvents true (**) Generic Mouse: always reports core events (**) Option Device /dev/input/mice (**) Option Emulate3Buttons true (**) Generic Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Generic Mouse: ZAxisMapping: buttons 4 and 5 (**) Generic Mouse: Buttons: 5 (II) XINPUT: Adding extended input device Generic Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) Generic Mouse: ps2EnableDataReporting: succeeded Warning: font renderer for .pcf already registered at priority 0 Warning: font renderer for .pcf.Z already registered at priority 0 Warning: font renderer for .pcf.gz already registered at priority 0 Warning: font renderer for .snf already registered at priority 0 Warning: font renderer for .snf.Z already registered at priority 0 Warning: font renderer for .snf.gz already registered at priority 0 Warning: font renderer for .bdf already registered at priority 0 Warning: font renderer for .bdf.Z already registered at priority 0 Warning: font renderer for .bdf.gz already registered at priority 0 Warning: font renderer for .pmf already registered at priority 0 (II) RADEON(0): [drm] removed 1 reserved context for kernel (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xff36a000 at 0x2a9dc4a000 = After which X will hang, then display garbage. Usually on the third or forth try, X starts and everything seems to work fine. I did a bit of Googling for similar situations, and someone suggested adding mousedev and pmouse to /etc/modules. If I do this, X starts on the first try, but the mouse doesn't work at all. I've checked to see that the mouse devices exist... [EMAIL PROTECTED]:~$ ls -al /dev/psaux /dev/input/mice crw-rw 1 root root 13, 63 2004-09-18 17:53 /dev/input/mice crw--- 1 root root 10, 1 2004-09-18 17:51 /dev/psaux I looked at /etc/X11/XF86Config-4 and found that I have entries for Configured Mouse at /dev/psaux and Generic Mouse at /dev/input/mice. This struck me as a bit odd, but I have an x86 machine running Debian Sarge... its XF86Config-4 is set up the same way and X has always worked flawlessly. However, I tried removing one or the other entry on my amd64 to see if this would help. Either it made no difference or X didn't work at all. Other relevant information... Video Card: ATI-Radeon 9200 (using debian ati driver) Kernel Version: 2.6.9-9-amd64-k8 XFree86 version: 4.3.0.1 Can someone tell me what's going on? I've run Fedora on this machine without any problems (well, without this problem), so I don't think it's a hardware issue... I can post my entire XF86Config-4 file and my XFree86 log files if it would help, but I thought I'd ask first. Thanks in advance. __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com
