Re: No sound, no mouse and now X applications won't start
On Tue, Jun 23, 2009 at 07:11:48PM +0530, Manish Jain wrote: > Hi, > > I have solved most of the problems listed in my previous message with > help from Roland Smith. > > The fact still remains that FreeBSD-7.2 has some definite problems on > AMD hardware : > > 1) On multi-core systems, the cores don't get initialized properly and > you get messages like : "AP #1 (PHY# 1) failed !" followed by panic. The > solution is to reboot, maybe as many as 6-7 times. Can you run the mptable command as root and post the output? > 2) The uhub/ums module fails to load and /dev/ums0 consequently won't > get created. The workaround is to unplug your USB mouse just before the > boot process begins, and plug it back in once you get the console. Since the USB stack has been replaced in 8-CURRENT, I'm not sure if many developers will want to spend time on this... > I have googled for the above 2 problems and there seem to many folks > suffering from the ills, with no solution except the ones I have listed > above. And these problems almost always occur on AMD multi-core systems. Most posts about the "AP #1 (PHY# 1) failed !" message that I found are several years old. > I hope the next release will address these problems, as well as a pretty > reasonable request from me much earlier to move vi from /usr/bin to > /bin. Even in single-user mode, you almost always need an editor. There is always /rescue/vi. And in single-user mode, you can always mount /usr if it is on a separate partition. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpzxBEF0g59U.pgp Description: PGP signature
Re: No sound, no mouse and now X applications won't start
On Tuesday 23 June 2009 15:41:48 Manish Jain wrote: > I hope the next release will address these problems, as well as a pretty > reasonable request from me much earlier to move vi from /usr/bin to > /bin. Even in single-user mode, you almost always need an editor. Which is why you have ed(1) - both in /bin and in /rescue - and /rescue/vi (although that needs a bit of tweaking due to the /etc/termcap problem). Bear in mind that /usr/bin/vi is over 300K, compared to the whole of /bin which is ~950K (if you avoid double-counting entries like /bin/csh and /bin/tcsh which are hardlinks to the same file), so you need to convince people who think /bin should stay small to let it grow by a third to save people learning ed(1). Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: No sound, no mouse and now X applications won't start
Message: 11 Date: Sat, 20 Jun 2009 16:34:00 -0400 From: Jerry Subject: Re: No sound, no mouse and now X applications won't start To: freebsd-questions@freebsd.org Message-ID: <20090620163400.62143...@scorpio.seibercom.net> Content-Type: text/plain; charset=US-ASCII On Sun, 21 Jun 2009 01:31:45 +0530 Manish Jain wrote: Looks like nobody at freebsd-questions has any answers for me. Maybe 7.2-x86 doesn't like newish amd hardware. post the output of: pciconf -lv as well as dmesg. Also your rc.conf and PolicyKit.conf files might be useful. -- Jerry ges...@yahoo.com Hi, I have solved most of the problems listed in my previous message with help from Roland Smith. The fact still remains that FreeBSD-7.2 has some definite problems on AMD hardware : 1) On multi-core systems, the cores don't get initialized properly and you get messages like : "AP #1 (PHY# 1) failed !" followed by panic. The solution is to reboot, maybe as many as 6-7 times. 2) The uhub/ums module fails to load and /dev/ums0 consequently won't get created. The workaround is to unplug your USB mouse just before the boot process begins, and plug it back in once you get the console. I have googled for the above 2 problems and there seem to many folks suffering from the ills, with no solution except the ones I have listed above. And these problems almost always occur on AMD multi-core systems. I hope the next release will address these problems, as well as a pretty reasonable request from me much earlier to move vi from /usr/bin to /bin. Even in single-user mode, you almost always need an editor. -- Regards Manish Jain invalid.poin...@gmail.com +91-96500-10329 Laast year I kudn't spell Software Engineer. Now I are won. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
OT: Dark humor (Re: No sound, no mouse and now X applications won't start)
Daniel Underwood wrote: > Aside: > > > My Bonnie looked into a gas tank, > > The height of its contents to see! > > She lit a small match to assist her, > > Oh, bring back my Bonnie to me. > > Hah... I like that. Dark, but witty. I first heard it some 50 years ago, and it was not new even then :) I wouldn't be surprised if it dated from the turn of the last century, when some gasoline-powered automobiles may not have had fuel gauges. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: No sound, no mouse and now X applications won't start
Aside: > My Bonnie looked into a gas tank, > The height of its contents to see! > She lit a small match to assist her, > Oh, bring back my Bonnie to me. Hah... I like that. Dark, but witty. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: No sound, no mouse and now X applications won't start
On Sun, Jun 21, 2009 at 01:31:45AM +0530, Manish Jain wrote: > > Hi Roland, > > Looks like nobody at freebsd-questions has any answers for me. Maybe > 7.2-x86 doesn't like newish amd hardware. Anyway, here are the > contents of /dev/sndstat : > > > FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386) > > Installed devices: > > pcm0: at cad 0 nid 1 on hdac0 kld > > snd_hda [MPSAFE] (1p:1v/0r:0v channels default) > > pcm1: at cad 0 nid 1 on hdac1 kld > > snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) > > pcm2: at cad 0 nid 1 on hdac1 kld > > snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) > > pcm3: at cad 0 nid 1 on hdac1 kld > > snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) > I tried snd_hda, even though it's listed as the driver for Intel > HDA, not Realtek HDA on AMD hardware. It doesn't work. The volume > control applet still complains no sound device has been configured. The fact that /dev/sndstat exists means that there is a sound driver that works. From the contents you can see that it is indeed the snd_hda driver ("HDA Realtek ALC885 "). You can also see that there are four sound outputs. Currently the digital HDMI is the default. You can configure the sound hardware through sysctls. If you run "sysctl hw.snd" you'll see a list of things you can change. With 'sysctl -d' you can see what a particular sysctl does. In this case one that is interesting is 'hw.snd.default_unit'. The different outputs in /dev/sndstat will be connected to different sockets on the machine (e.g. front/back panel). Try setting hw.snd.default_unit to 1, 2 or 3 and see if that helps. It could be that you have to unload and reload the snd_hda module after setting the default channel. You might also have to restart the volume control applet. > /dev/ums0 does get created I if plug in the mouse after the login > prompt has appeared. Ok. I think it should be a bug that the mouse isn't properly detected when connected at boot, but since the USB stack has been replaced in 8-CURRENT, I don't know if anyone is willing to go bughunting in the 7.x USB stack. > But the mouse would behave crazy till I changed the Xorg generated > xorg.conf's setting of ZAxisMapping from "4 5 6 7" to "4 5". That is not abnormal. A lot of mice need special zaxis mappings. > I have still more problems. After all ports finished installing, > some X applications just don't start (eg Acroread). I can't any > error messages from the terminal because gnome-terminal itself > doesn't start. Then use an xterm instead of a gnome-terminal. Acroread depends on Linux emulation. Maybe you're missing some bits there? > Given time, maybe I could ultimately figure this problem out, but if > you have any ready ideas, please be kind enough to share them me. > > Here are some messages. > #/var/log/console.log : > > Jun 20 01:17:01 pbbi kernel: Jun 20 01:17:01 pbbi pulseaudio[1276]: main.c: > > Daemon startup without any loaded modules, refusing to work. I've never used pulseaudio. I prefer esound. > > Jun 20 01:18:04 pbbi kernel: Jun 20 01:18:04 pbbi > > gnome-keyring-daemon[1251]: dbus failure unregistering from session: > > Connection is closed This looks pretty harmless. > #/var/log/messages : > > Jun 20 02:00:07 pbbi kernel: info: [drm] Loading RS780 CP Microcode > > Jun 20 02:00:07 pbbi kernel: info: [drm] Loading RS780 PFP Microcode > > Jun 20 02:00:07 pbbi kernel: info: [drm] Resetting GPU > > Jun 20 02:00:07 pbbi kernel: info: [drm] writeback test succeeded in 1 usecs > > Jun 20 02:00:07 pbbi kernel: drm0: [ITHREAD] > > Jun 20 02:00:07 pbbi console-kit-daemon[1135]: WARNING: kvm_getenvv failed Look at kvm_getenvv(3), in the BUGS section: "In order for kvm_getenvv(3) to function correctly, procfs(5) must be mounted on /proc" > loader.conf looks like following : > > kern.maxdsiz="734003200" > > ums_load="YES" > > linprocfs_load="YES" > > linsysfs_load="YES" > > sound_load="YES" > > snd_hda_load="YES" Looks OK. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpfFPTsBATGd.pgp Description: PGP signature
Re: No sound, no mouse and now X applications won't start
On Sun, 21 Jun 2009 01:31:45 +0530 Manish Jain wrote: > Looks like nobody at freebsd-questions has any answers for me. Maybe > 7.2-x86 doesn't like newish amd hardware. post the output of: pciconf -lv as well as dmesg. Also your rc.conf and PolicyKit.conf files might be useful. -- Jerry ges...@yahoo.com My Bonnie looked into a gas tank, The height of its contents to see! She lit a small match to assist her, Oh, bring back my Bonnie to me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
No sound, no mouse and now X applications won't start
Hi Roland, Looks like nobody at freebsd-questions has any answers for me. Maybe 7.2-x86 doesn't like newish amd hardware. Anyway, here are the contents of /dev/sndstat : FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386) Installed devices: pcm0: at cad 0 nid 1 on hdac0 kld snd_hda [MPSAFE] (1p:1v/0r:0v channels default) pcm1: at cad 0 nid 1 on hdac1 kld snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) pcm2: at cad 0 nid 1 on hdac1 kld snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) pcm3: at cad 0 nid 1 on hdac1 kld snd_hda [MPSAFE] (1p:1v/1r:1v channels duplex) I tried snd_hda, even though it's listed as the driver for Intel HDA, not Realtek HDA on AMD hardware. It doesn't work. The volume control applet still complains no sound device has been configured. /dev/ums0 does get created I if plug in the mouse after the login prompt has appeared. But the mouse would behave crazy till I changed the Xorg generated xorg.conf's setting of ZAxisMapping from "4 5 6 7" to "4 5". I have still more problems. After all ports finished installing, some X applications just don't start (eg Acroread). I can't any error messages from the terminal because gnome-terminal itself doesn't start. Given time, maybe I could ultimately figure this problem out, but if you have any ready ideas, please be kind enough to share them me. Here are some messages. #/var/log/console.log : Jun 20 01:17:01 pbbi kernel: Jun 20 01:17:01 pbbi pulseaudio[1276]: main.c: Daemon startup without any loaded modules, refusing to work. Jun 20 01:18:04 pbbi kernel: Jun 20 01:18:04 pbbi gnome-keyring-daemon[1251]: dbus failure unregistering from session: Connection is closed Jun 20 01:21:50 pbbi kernel: Jun 20 01:21:50 pbbi pulseaudio[1686]: main.c: Daemon startup without any loaded modules, refusing to work. Jun 20 01:21:51 pbbi kernel: Jun 20 01:21:51 pbbi dbus-daemon: Would reject message, 1 matched rules; type="method_call", sender=":1.10" (uid=0 pid=1292 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.SystemToolsBackends.Platform" (uid=0 pid=1723 comm=")) Jun 20 01:21:51 pbbi kernel: Jun 20 01:21:51 pbbi dbus-daemon: Would reject message, 1 matched rules; type="method_call", sender=":1.10" (uid=0 pid=1292 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.SystemToolsBackends.Platform" (uid=0 pid=1723 comm=")) Jun 20 01:22:04 pbbi kernel: Jun 20 01:22:04 pbbi gnome-keyring-daemon[1665]: dbus failure unregistering from session: Connection is closed Jun 20 02:00:18 pbbi kernel: Jun 20 02:00:18 pbbi pulseaudio[2068]: main.c: Daemon startup without any loaded modules, refusing to work. Jun 20 02:00:19 pbbi kernel: Jun 20 02:00:19 pbbi dbus-daemon: Would reject message, 1 matched rules; type="method_call", sender=":1.10" (uid=0 pid=1292 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.SystemToolsBackends.Platform" (uid=0 pid=1723 comm=")) Jun 20 02:00:19 pbbi kernel: Jun 20 02:00:19 pbbi dbus-daemon: Would reject message, 1 matched rules; type="method_call", sender=":1.10" (uid=0 pid=1292 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.SystemToolsBackends.Platform" (uid=0 pid=1723 comm=")) Jun 20 02:22:14 pbbi kernel: Jun 20 02:22:14 pbbi pulseaudio[7162]: main.c: Daemon startup without any loaded modules, refusing to work. Jun 20 02:22:14 pbbi kernel: Jun 20 02:22:14 pbbi dbus-daemon: Would reject message, 1 matched rules; type="method_call", sender=":1.10" (uid=0 pid=1292 comm=") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination="org.freedesktop.SystemToolsBackends.Platform" (uid=0 pid=1723 comm=")) #/var/log/messages : Jun 20 02:00:07 pbbi kernel: info: [drm] Loading RS780 CP Microcode Jun 20 02:00:07 pbbi kernel: info: [drm] Loading RS780 PFP Microcode Jun 20 02:00:07 pbbi kernel: info: [drm] Resetting GPU Jun 20 02:00:07 pbbi kernel: info: [drm] writeback test succeeded in 1 usecs Jun 20 02:00:07 pbbi kernel: drm0: [ITHREAD] Jun 20 02:00:07 pbbi console-kit-daemon[1135]: WARNING: kvm_getenvv failed Jun 20 02:00:07 pbbi gnome-session[2036]: WARNING: Unable to determine session: Unable to lookup session information for process '2036' Jun 20 02:00:18 pbbi gnome-session[2036]: WARNING: Application 'metacity.desktop' failed to register before timeout Jun 20 02:00:18 pbbi pulseaudio[2068]: main.c: Daemon startup without any loaded modules, refusing to work. Jun 20 02:00:19 pbbi console-kit-daemon[1135]: WARNING: kvm_getenvv failed Jun 20 02:00:19 pbbi console-kit-daemon[1135]: WARNING: kvm_getenvv failed Jun 20 02:00:19 pbbi dbus-daemon: Would reject message, 1 matc