From Missmolly1944 at aol.com Fri May 1 18:18:23 2009 From: Missmolly1944 at aol.com (Missmolly1944@aol.com) Date: Fri May 1 19:43:24 2009 Subject: Hard drive for Dell Inspiron 5000e - place to buy Message-ID: Hi, how much for the hard drive? Lou **************Access 350+ FREE radio stations anytime from anywhere on the web. Get the Radio Toolbar! (http://toolbar.aol.com/aolradio/download.html?ncid=emlcntusdown00000003) From mav at FreeBSD.org Sat May 2 07:36:27 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sat May 2 07:36:33 2009 Subject: Hard drive for Dell Inspiron 5000e - place to buy In-Reply-To: <1241220186.00106926.1241207403@10.7.7.3> References: <1241220186.00106926.1241207403@10.7.7.3> Message-ID: <49FBE9E6.4000806@FreeBSD.org> Missmolly1944@aol.com wrote: > Hi, how much for the hard drive? Lou I have bought OCZ Vertex 60GB SSD instead of my Acer laptop hard drive. It is quite expensive and not so big, but it is incredibly fast! I am completely satisfied with it. -- Alexander Motin From ivakras1 at gmail.com Sun May 3 15:41:35 2009 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Sun May 3 15:41:40 2009 Subject: Hard drive for Dell Inspiron 5000e - place to buy In-Reply-To: References: Message-ID: <200905031939.16089.ivakras1@gmail.com> On ??????? 01 ??? 2009 22:03:47 Missmolly1944@aol.com wrote: > Hi, how much for the hard drive? Lou > **************Access 350+ FREE radio stations anytime from anywhere on the > web. Get the Radio Toolbar! > (http://toolbar.aol.com/aolradio/download.html?ncid=emlcntusdown00000003) > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > That is subject for me. My WDC-WD2500BEVS hdd is about 56-60C in idle, i can't handle laptop on laps. Power consumption is very high, less than 1 hour on battery. Thinking about SSD. From mav at FreeBSD.org Sun May 3 22:18:25 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sun May 3 22:18:38 2009 Subject: Fighting for the power. Message-ID: <49FE1826.4060000@FreeBSD.org> I would like to summarize some of my knowledge on reducing FreeBSD power consumption and describe some new things I have recently implemented in 8-CURRENT. The main character of this story is my 12" Acer TravelMate 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under amd64 8-CURRENT. Modern systems, especially laptops, are implementing big number of power-saving technologies. Some of them are working automatically, other have significant requirements and need special system tuning or trade-offs to be effectively used. So here is the steps: 1. CPU CPU is the most consuming part of the system. Under the full load it alone may consume more then 40W of power, but for real laptop usage the most important is idle consumption. Core2Duo T7700 CPU has 2 cores, runs on 2.4GHz frequency, supports EIST technology with P-states at 2400, 2000, 1600, 1200 and 800MHz levels, supports C1, C2 and C3 idle C-states, plus throttling. So how can we use it: P-states and throttling Enabling powerd allows to effectively control CPU frequency/voltage depending on CPU load. powerd on recent system can handle it quite transparently. By default, frequency controlled via mix of EIST and throttling technologies. First one controls both core frequency and voltage, second - only core frequency. Both technologies give positive power-saving effect. But effect of throttling is small and can be completely hidden by using C2 state, that's why I recommend to disable throttling control by adding to /boot/loader.conf: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 In my case frequency/voltage control saves about 5W of idle power. C-states - C1 stops clock on some parts of CPU core during inactivity. It is safe, cheap and supported by CPUs for ages. System uses C1 state by default. - C2 state allows CPU to turn off all core clocks on idle. It is also cheap, but requires correct ACPI-chipset-CPU interoperation to be used. Use of C2 state can be enabled by adding to /etc/rc.conf: performance_cx_lowest="C2" economy_cx_lowest="C2" Effect from this state is not so big when powerd is used, but still noticeable, - C3 state allows CPU completely stop all internal clocks, reduce voltage and disconnect from system bus. This state gives additional power saving effect, but it is not cheap and require trade-offs. As soon as CPU is completely stopped in C3 state, local APIC timers in each CPU core, used by FreeBSD as event sources on SMP, are not functioning. It stops system time, breaks scheduling that makes system close to dead. The only solution for this problem is to use some external timers. Originally, before SMP era, FreeBSD used i8254 (for HZ) and RTC (for stats) chipset timers. I have made changes to 8-CURRENT to resurrect them for SMP systems. To use them, you can disable local APIC timers by adding to /boot/loader.conf: hint.apic.0.clock=0 Also, to drop/rise voltage on C3, CPU needs time (57us for my system). It means that C3 state can't be effectively used when system is waking up often. To increase inactivity periods we should reduce interrupt rate as much as possible by adding to loader.conf: kern.hz=100 It may increase system response time a bit, but it is not significant for laptop. Also we may avoid additional 128 interrupts per second per core, by the cost of scheduling precision, with using i8254 timer also for statistic collection purposes instead of RTC clock, by using another newly added option: hint.atrtc.0.clock=0 As result, system has only 100 interrupts per core and CPUs are using C3 with high efficiency: %sysctl dev.cpu |grep cx dev.cpu.0.cx_supported: C1/1 C2/1 C3/57 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 0.00% 0.00% 100.00% last 7150us dev.cpu.1.cx_supported: C1/1 C2/1 C3/57 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.00% 0.00% 100.00% last 2235us Result of effective C3 state usage, comparing to C2+powerd, is about 2W. 2. PCI devices PCI bus provides method to control device power. For example, I have completely no use for my FireWire controller and most of time - EHCI USB controller. Disabling them allows me to save about 3W of power. To disable all unneeded PCI devices you should build kernel without their drivers and add to loader.conf: hw.pci.do_power_nodriver=3 To enable devices back all you need to do is just load their drivers as modules. 3. Radios WiFi and Bluetooth adapters can consume significant power when used (up to 2W when my iwn WiFi is connected) or just enabled (0.5W). Disabling them with mechanical switch on laptop case saves energy even when they are not connected. 4. HDA modem I was surprised, but integrated HDA modem consumed about 1W of power even when not used. I have used the most radical solution - removed it mechanically from socket. Case surface in that area become much cooler. 5. HDA sound To reduce number of sound generated interrupts I have added to the loader.conf: hint.pcm.0.buffersize=65536 hint.pcm.1.buffersize=65536 hw.snd.feeder_buffersize=65536 hw.snd.latency=7 6. HDD First common recommendation is use tmpfs for temporary files. RAM is cheap, fast and anyway with you. Also you may try to setup automatic idle drive spin-down, but if it is the only system drive you should be careful, as every spin-up reduces drive's life time. For several months (until I have bought SATA SSD) I have successfully used SDHC card in built-in PCI sdhci card reader as main filesystem. On random read requests it is much faster then HDD, but it is very slow on random write. Same time it consumes almost nothing. USB drives could also be used, but effect is much less as EHCI USB controller consumes much power. Spinning-down my 2.5" Hitachi SATA HDD saves about 1W of power. Removing it completely saves 2W. 7. SATA Comparing to PATA, SATA interface uses differential signaling for data transfer. To work properly it has to transmit pseudo-random scrambled sequence even when idle. As you understand, that requires power. But SATA implements two power saving modes: PARTIAL and SLUMBER. These modes could be activated by either host or device if both sides support them. PARTIAL mode just stops scrambling, but keeps neutral link state, resume time is 50-100us. SLUMBER mode powers down interface completely, but respective resume time is 3-10ms. I have added minimal SATA power management to AHCI driver. There are hint.ata.X.pm_level loader tunables can be used to control it now. Setting it to 1 allows drive itself to initiate power saving, when it wish. Values 2 and 3 make AHCI controller to initiate PARTIAL and SLUMBER transitions after every command completion. Note that SATA power saving is not compatible with drive hot-swap, as controller unable to detect drive presence when link is powered-down. In my case PARTIAL mode saves 0.5W and SLUMBER - 0.8W of power. So what have I got? To monitor real system power consumption I am using information provided by ACPI battery via `acpiconf -i0` command: Original system: Design capacity: 4800 mAh Last full capacity: 4190 mAh Technology: secondary (rechargeable) Design voltage: 11100 mV Capacity (warn): 300 mAh Capacity (low): 167 mAh Low/warn granularity: 32 mAh Warn/full granularity: 32 mAh Model number: Victoria Serial number: 292 Type: LION OEM info: SIMPLO State: discharging Remaining capacity: 93% Remaining time: 2:24 Present rate: 1621 mA Voltage: 12033 mV Tuned system: %acpiconf -i0 Design capacity: 4800 mAh Last full capacity: 4190 mAh Technology: secondary (rechargeable) Design voltage: 11100 mV Capacity (warn): 300 mAh Capacity (low): 167 mAh Low/warn granularity: 32 mAh Warn/full granularity: 32 mAh Model number: Victoria Serial number: 292 Type: LION OEM info: SIMPLO State: discharging Remaining capacity: 94% Remaining time: 4:47 Present rate: 826 mA Voltage: 12231 mV So I have really doubled my on-battery time by this tuning - 4:47 hours instead of 2:24 with default settings. Preinstalled vendor-tuned Windows XP on the same system, provides maximum 3:20 hours. -- Alexander Motin From nate at root.org Sun May 3 23:44:31 2009 From: nate at root.org (Nate Lawson) Date: Sun May 3 23:44:37 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <49FE29A4.30507@root.org> Alexander Motin wrote: > I would like to summarize some of my knowledge on reducing FreeBSD power > consumption and describe some new things I have recently implemented in > 8-CURRENT. The main character of this story is my 12" Acer TravelMate > 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under > amd64 8-CURRENT. Very nice summary. Thanks for doing the research. > P-states and throttling > Enabling powerd allows to effectively control CPU frequency/voltage > depending on CPU load. powerd on recent system can handle it quite > transparently. By default, frequency controlled via mix of EIST and > throttling technologies. First one controls both core frequency and > voltage, second - only core frequency. Both technologies give positive > power-saving effect. But effect of throttling is small and can be > completely hidden by using C2 state, that's why I recommend to disable > throttling control by adding to /boot/loader.conf: > hint.p4tcc.0.disabled=1 > hint.acpi_throttle.0.disabled=1 When I first wrote cpufreq, there was some question if vendors (even non-Intel) might use throttling for more than just cutting the duty cycle. It turns out they haven't, and have focused more on dropping the voltage with P-state transitions (EIST, PowerNow) and are treating throttling as a legacy feature. The time may have come to disable p4tcc and throttling by default, as long as it's easy for a user to enable them again. Perhaps just a change to boot/default/device.hints? > In my case frequency/voltage control saves about 5W of idle power. > C-states > - C1 stops clock on some parts of CPU core during inactivity. It is > safe, cheap and supported by CPUs for ages. System uses C1 state by > default. > - C2 state allows CPU to turn off all core clocks on idle. It is also > cheap, but requires correct ACPI-chipset-CPU interoperation to be used. > Use of C2 state can be enabled by adding to /etc/rc.conf: > performance_cx_lowest="C2" > economy_cx_lowest="C2" The default settings in rc.conf should allow the lowest Cx setting available to be used. Perhaps that changed? Really, we want C3+ to be enabled by default without the user doing anything. > - C3 state allows CPU completely stop all internal clocks, reduce > voltage and disconnect from system bus. This state gives additional > power saving effect, but it is not cheap and require trade-offs. > As soon as CPU is completely stopped in C3 state, local APIC timers in > each CPU core, used by FreeBSD as event sources on SMP, are not > functioning. It stops system time, breaks scheduling that makes system > close to dead. The only solution for this problem is to use some > external timers. Originally, before SMP era, FreeBSD used i8254 (for HZ) > and RTC (for stats) chipset timers. I have made changes to 8-CURRENT to > resurrect them for SMP systems. To use them, you can disable local APIC > timers by adding to /boot/loader.conf: > hint.apic.0.clock=0 > Also, to drop/rise voltage on C3, CPU needs time (57us for my system). > It means that C3 state can't be effectively used when system is waking > up often. To increase inactivity periods we should reduce interrupt rate > as much as possible by adding to loader.conf: > kern.hz=100 Yeah, hz=1000 doesn't make sense for laptops and I use hz=100 everywhere. > It may increase system response time a bit, but it is not significant > for laptop. Also we may avoid additional 128 interrupts per second per > core, by the cost of scheduling precision, with using i8254 timer also > for statistic collection purposes instead of RTC clock, by using another > newly added option: > hint.atrtc.0.clock=0 The real solution for C3 (and C4, etc.) is to implement tickless scheduling and to fix the current dependence on LAPIC for timer interrupts. Hopefully someone will do that soon. With that change, this change isn't needed. > 4. HDA modem > I was surprised, but integrated HDA modem consumed about 1W of power > even when not used. I have used the most radical solution - removed it > mechanically from socket. Case surface in that area become much cooler. Most modems support the ACPI Dx states, where D3 = device powered off. I'd think the PCI "power no driver option" would disable the soft modem since it's unlikely you have a driver for it. > 6. HDD > First common recommendation is use tmpfs for temporary files. RAM is > cheap, fast and anyway with you. > Also you may try to setup automatic idle drive spin-down, but if it is > the only system drive you should be careful, as every spin-up reduces > drive's life time. Did you increase the fsflush delay also? > So I have really doubled my on-battery time by this tuning - 4:47 hours > instead of 2:24 with default settings. Preinstalled vendor-tuned Windows > XP on the same system, provides maximum 3:20 hours. Very nice. I think tickless scheduling is the single largest win for power mgmt we could get. Second best would be S4 (suspend to disk). -- Nate From mcdouga9 at egr.msu.edu Mon May 4 01:30:56 2009 From: mcdouga9 at egr.msu.edu (Adam McDougall) Date: Mon May 4 01:31:08 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <20090504011421.GI6901@egr.msu.edu> On Mon, May 04, 2009 at 01:18:14AM +0300, Alexander Motin wrote: I would like to summarize some of my knowledge on reducing FreeBSD power consumption and describe some new things I have recently implemented in 8-CURRENT. The main character of this story is my 12" Acer TravelMate 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under amd64 8-CURRENT. Great list! May I suggest screen brightness and DPMS as another tool to save power, I've measured a 5W difference from the screen draw. Keeping the brightness as low as tolerable helps considerably, but also using 'xset dpms 120 120 120' (modify to taste) in .xinitrc to turn off the screen after 2 minutes helps when the laptop isn't being used every second. May need this in xorg.conf: Option "dpms" From mav at FreeBSD.org Mon May 4 03:19:42 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 4 03:20:00 2009 Subject: Fighting for the power. In-Reply-To: <49FE29A4.30507@root.org> References: <49FE1826.4060000@FreeBSD.org> <49FE29A4.30507@root.org> Message-ID: <49FE5EC8.3040205@FreeBSD.org> Nate Lawson wrote: > The time may have come to disable p4tcc and throttling by default, as > long as it's easy for a user to enable them again. Perhaps just a change > to boot/default/device.hints? They still could be effective for old P4 series which had no C1E/C2 idle states support yet. But probably their power consumption is not so interesting area now. > The default settings in rc.conf should allow the lowest Cx setting > available to be used. Perhaps that changed? Really, we want C3+ to be > enabled by default without the user doing anything. Present defaults are to use C1. Probably we can allow C2 use more or less safely. Due to default LAPIC timer problems, enabling C3+ by default will make system dead by default. > Yeah, hz=1000 doesn't make sense for laptops and I use hz=100 everywhere. Without using C3+ it is not so important. I haven't seen any power difference. C1/C2 have practically zero exit latency, while power consumed by interrupt handler itself is miserable. > The real solution for C3 (and C4, etc.) is to implement tickless > scheduling and to fix the current dependence on LAPIC for timer > interrupts. Hopefully someone will do that soon. With that change, this > change isn't needed. System will always have tons of waiting callouts and timeouts to be handled. So timer will be always needed. Working timer. >> 4. HDA modem >> I was surprised, but integrated HDA modem consumed about 1W of power >> even when not used. I have used the most radical solution - removed it >> mechanically from socket. Case surface in that area become much cooler. > > Most modems support the ACPI Dx states, where D3 = device powered off. > I'd think the PCI "power no driver option" would disable the soft modem > since it's unlikely you have a driver for it. Modem share HDA bus/controller with sound. So PCI D3 will kill sound also, that is not an option. snd_hda driver itself puts all non-audio codecs into the HDA D3 state, but in my case it was not effective. >> 6. HDD >> First common recommendation is use tmpfs for temporary files. RAM is >> cheap, fast and anyway with you. >> Also you may try to setup automatic idle drive spin-down, but if it is >> the only system drive you should be careful, as every spin-up reduces >> drive's life time. > > Did you increase the fsflush delay also? I don't, but how long can it delay requests? Several minutes? Hour? Then there is high probability of data loss. Actually I have tried to reduce number of idle disk write activity, but I haven't very succeeded. Even in my quite simple icewm X environment something was persistently writing something every several minutes. I have found and disabled some activity sources, but it was not enough. What would happen in some complicated KDE/Gnome environment I am just afraid to think. -- Alexander Motin From mav at FreeBSD.org Mon May 4 03:45:15 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 4 03:45:22 2009 Subject: Fighting for the power. In-Reply-To: <20090504011421.GI6901@egr.msu.edu> References: <49FE1826.4060000@FreeBSD.org> <20090504011421.GI6901@egr.msu.edu> Message-ID: <49FE64C5.2020507@FreeBSD.org> Adam McDougall wrote: > On Mon, May 04, 2009 at 01:18:14AM +0300, Alexander Motin wrote: > > I would like to summarize some of my knowledge on reducing FreeBSD power > consumption and describe some new things I have recently implemented in > 8-CURRENT. The main character of this story is my 12" Acer TravelMate > 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under > amd64 8-CURRENT. > > Great list! May I suggest screen brightness and DPMS as another tool > to save power, I've measured a 5W difference from the screen draw. > Keeping the brightness as low as tolerable helps considerably, but > also using 'xset dpms 120 120 120' (modify to taste) in .xinitrc to > turn off the screen after 2 minutes helps when the laptop isn't being > used every second. May need this in xorg.conf: > Option "dpms" Yes, backlight is also important. But there is not so much things could be done. When I am leaving system for some time, I can just close the lid, if not put system into S3 state, which require very small power (at least I was unable to really measure it without all-day-long testing). Thanks to jkim@ we have more or less working S3 state for amd64 now. -- Alexander Motin From mav at FreeBSD.org Mon May 4 07:50:25 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 4 07:50:37 2009 Subject: Fighting for the power. In-Reply-To: <200905040926.38337.hselasky@c2i.net> References: <49FE1826.4060000@FreeBSD.org> <200905040926.38337.hselasky@c2i.net> Message-ID: <49FE9E3B.1050509@FreeBSD.org> Hans Petter Selasky wrote: >> 2. PCI devices >> PCI bus provides method to control device power. For example, I have >> completely no use for my FireWire controller and most of time - EHCI USB >> controller. Disabling them allows me to save about 3W of power. To >> disable all unneeded PCI devices you should build kernel without their >> drivers and add to loader.conf: >> hw.pci.do_power_nodriver=3 >> To enable devices back all you need to do is just load their drivers as >> modules. > > The new USB stack should turn off USB HC's automatically when not in use. At > least the schedules will get disabled. Did you do any research on this? Sorry, I really was testing it only with previous USB stack. Now I can acknowledge, that new ehci module loading adds only 0.2W for me by default and almost nothing if I power down built-in USB2 web cam connected to it using `usbconfig -u 5 -a 2 power_off`. Great! Thanks! -- Alexander Motin From hselasky at c2i.net Mon May 4 08:24:07 2009 From: hselasky at c2i.net (Hans Petter Selasky) Date: Mon May 4 08:24:14 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <200905040926.38337.hselasky@c2i.net> > 2. PCI devices > PCI bus provides method to control device power. For example, I have > completely no use for my FireWire controller and most of time - EHCI USB > controller. Disabling them allows me to save about 3W of power. To > disable all unneeded PCI devices you should build kernel without their > drivers and add to loader.conf: > hw.pci.do_power_nodriver=3 > To enable devices back all you need to do is just load their drivers as > modules. The new USB stack should turn off USB HC's automatically when not in use. At least the schedules will get disabled. Did you do any research on this? --HPS From onemda at gmail.com Mon May 4 09:40:43 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon May 4 09:40:54 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> On 5/4/09, Alexander Motin wrote: > 2. PCI devices > PCI bus provides method to control device power. For example, I have > completely no use for my FireWire controller and most of time - EHCI USB > controller. Disabling them allows me to save about 3W of power. To > disable all unneeded PCI devices you should build kernel without their > drivers and add to loader.conf: > hw.pci.do_power_nodriver=3 > To enable devices back all you need to do is just load their drivers as > modules. Unloading modules doesnt put them back into into D3 state. You are forced to load some another module again to put wanted device into D3 state. -- Paul From mav at FreeBSD.org Mon May 4 09:51:11 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 4 09:51:29 2009 Subject: Fighting for the power. In-Reply-To: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> References: <49FE1826.4060000@FreeBSD.org> <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> Message-ID: <49FEBA89.4040609@FreeBSD.org> Paul B. Mahol wrote: > On 5/4/09, Alexander Motin wrote: >> 2. PCI devices >> PCI bus provides method to control device power. For example, I have >> completely no use for my FireWire controller and most of time - EHCI USB >> controller. Disabling them allows me to save about 3W of power. To >> disable all unneeded PCI devices you should build kernel without their >> drivers and add to loader.conf: >> hw.pci.do_power_nodriver=3 >> To enable devices back all you need to do is just load their drivers as >> modules. > > Unloading modules doesnt put them back into into D3 state. > You are forced to load some another module again to put wanted device > into D3 state. Yes. Resume also does not powers down unowned devices. Would be good to fix that also. -- Alexander Motin From mav at FreeBSD.org Mon May 4 12:24:33 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 4 12:24:40 2009 Subject: Fighting for the power. In-Reply-To: <1241438990.1280.6.camel@RabbitsDen> References: <49FE1826.4060000@FreeBSD.org> <1241438990.1280.6.camel@RabbitsDen> Message-ID: <49FEDE7B.30804@FreeBSD.org> Alexandre "Sunny" Kovalenko wrote: > On Mon, 2009-05-04 at 01:18 +0300, Alexander Motin wrote: >> - C3 state allows CPU completely stop all internal clocks, reduce >> voltage and disconnect from system bus. This state gives additional >> power saving effect, but it is not cheap and require trade-offs. >> As soon as CPU is completely stopped in C3 state, local APIC timers in >> each CPU core, used by FreeBSD as event sources on SMP, are not >> functioning. It stops system time, breaks scheduling that makes system >> close to dead. > Did you try to see whether putting one of the cores in C3 state by doing > something like > > dev.cpu.1.cx_lowest=C3 > > makes any difference? > > # sysctl dev.cpu | grep cx_usage > dev.cpu.0.cx_usage: 0.00% 100.00% 0.00% > dev.cpu.1.cx_usage: 0.00% 5.18% 94.81% I did. As soon as first CPU core is not in C3 state, second core unable to enter C3 completely and disconnect from the bus, as cores are sharing common resources. Such technique allows to avoid LAPIC timer problems, but I haven't noticed any effect from this on CPU idle power. The only difference I have noticed was in the case, when first core is busy. C3 on second idle core then somehow reduces summary consumption a bit. In other words, C3 state should be active on both cores simultaneously to give real effect. -- Alexander Motin From gaijin.k at gmail.com Mon May 4 13:12:27 2009 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Mon May 4 13:12:40 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <1241438990.1280.6.camel@RabbitsDen> On Mon, 2009-05-04 at 01:18 +0300, Alexander Motin wrote: > I would like to summarize some of my knowledge on reducing FreeBSD power > consumption and describe some new things I have recently implemented in > 8-CURRENT. The main character of this story is my 12" Acer TravelMate > 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under > amd64 8-CURRENT. > > Modern systems, especially laptops, are implementing big number of > power-saving technologies. Some of them are working automatically, other > have significant requirements and need special system tuning or > trade-offs to be effectively used. > > So here is the steps: > > 1. CPU > CPU is the most consuming part of the system. Under the full load it > alone may consume more then 40W of power, but for real laptop usage the > most important is idle consumption. > Core2Duo T7700 CPU has 2 cores, runs on 2.4GHz frequency, supports EIST > technology with P-states at 2400, 2000, 1600, 1200 and 800MHz levels, > supports C1, C2 and C3 idle C-states, plus throttling. So how can we use it: > P-states and throttling > Enabling powerd allows to effectively control CPU frequency/voltage > depending on CPU load. powerd on recent system can handle it quite > transparently. By default, frequency controlled via mix of EIST and > throttling technologies. First one controls both core frequency and > voltage, second - only core frequency. Both technologies give positive > power-saving effect. But effect of throttling is small and can be > completely hidden by using C2 state, that's why I recommend to disable > throttling control by adding to /boot/loader.conf: > hint.p4tcc.0.disabled=1 > hint.acpi_throttle.0.disabled=1 > In my case frequency/voltage control saves about 5W of idle power. > C-states > - C1 stops clock on some parts of CPU core during inactivity. It is > safe, cheap and supported by CPUs for ages. System uses C1 state by default. > - C2 state allows CPU to turn off all core clocks on idle. It is also > cheap, but requires correct ACPI-chipset-CPU interoperation to be used. > Use of C2 state can be enabled by adding to /etc/rc.conf: > performance_cx_lowest="C2" > economy_cx_lowest="C2" > Effect from this state is not so big when powerd is used, but still > noticeable, > - C3 state allows CPU completely stop all internal clocks, reduce > voltage and disconnect from system bus. This state gives additional > power saving effect, but it is not cheap and require trade-offs. > As soon as CPU is completely stopped in C3 state, local APIC timers in > each CPU core, used by FreeBSD as event sources on SMP, are not > functioning. It stops system time, breaks scheduling that makes system > close to dead. Did you try to see whether putting one of the cores in C3 state by doing something like dev.cpu.1.cx_lowest=C3 makes any difference? # sysctl dev.cpu | grep cx_usage dev.cpu.0.cx_usage: 0.00% 100.00% 0.00% dev.cpu.1.cx_usage: 0.00% 5.18% 94.81% -- Alexandre Kovalenko (????????? ?????????) From oberman at es.net Mon May 4 15:10:02 2009 From: oberman at es.net (Kevin Oberman) Date: Mon May 4 15:10:14 2009 Subject: Fighting for the power. In-Reply-To: Your message of "Mon, 04 May 2009 15:24:27 +0300." <49FEDE7B.30804@FreeBSD.org> Message-ID: <20090504150959.67BE91CC50@ptavv.es.net> > Date: Mon, 04 May 2009 15:24:27 +0300 > From: Alexander Motin > Sender: owner-freebsd-mobile@freebsd.org > > Alexandre "Sunny" Kovalenko wrote: > > On Mon, 2009-05-04 at 01:18 +0300, Alexander Motin wrote: > >> - C3 state allows CPU completely stop all internal clocks, reduce > >> voltage and disconnect from system bus. This state gives additional > >> power saving effect, but it is not cheap and require trade-offs. > >> As soon as CPU is completely stopped in C3 state, local APIC timers in > >> each CPU core, used by FreeBSD as event sources on SMP, are not > >> functioning. It stops system time, breaks scheduling that makes system > >> close to dead. > > Did you try to see whether putting one of the cores in C3 state by doing > > something like > > > > dev.cpu.1.cx_lowest=C3 > > > > makes any difference? > > > > # sysctl dev.cpu | grep cx_usage > > dev.cpu.0.cx_usage: 0.00% 100.00% 0.00% > > dev.cpu.1.cx_usage: 0.00% 5.18% 94.81% > > I did. As soon as first CPU core is not in C3 state, second core unable > to enter C3 completely and disconnect from the bus, as cores are sharing > common resources. Such technique allows to avoid LAPIC timer problems, > but I haven't noticed any effect from this on CPU idle power. The only > difference I have noticed was in the case, when first core is busy. C3 > on second idle core then somehow reduces summary consumption a bit. > > In other words, C3 state should be active on both cores simultaneously > to give real effect. It is important to be aware that the presence of USB will keep a system from entering C3. Either build a kernel without USB and load it only whan needed or run 8-CURRENT with the USB2 stack which is purported to fix this problem. (I have no systems running CURRENT, so I can't confirm that USB2 fixes the problem.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From lwindschuh at googlemail.com Mon May 4 18:40:42 2009 From: lwindschuh at googlemail.com (Lucius Windschuh) Date: Mon May 4 18:41:14 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <90a5caac0905041119h70101d12i56863e57b27d2e55@mail.gmail.com> 2009/5/4 Alexander Motin : > I would like to summarize some of my knowledge on reducing FreeBSD power > consumption and describe some new things I have recently implemented in > 8-CURRENT. The main character of this story is my 12" Acer TravelMate > 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under > amd64 8-CURRENT. First, thank you for your report about power saving on current laptops. :-) > 1. CPU > [...] > ?- C3 state allows CPU completely stop all internal clocks, reduce > voltage and disconnect from system bus. This state gives additional > power saving effect, but it is not cheap and require trade-offs. > As soon as CPU is completely stopped in C3 state, local APIC timers in > each CPU core, used by FreeBSD as event sources on SMP, are not > functioning. It stops system time, breaks scheduling that makes system > close to dead. The only solution for this problem is to use some > external timers. Originally, before SMP era, FreeBSD used i8254 (for HZ) > and RTC (for stats) chipset timers. I have made changes to 8-CURRENT to > resurrect them for SMP systems. To use them, you can disable local APIC > timers by adding to /boot/loader.conf: > hint.apic.0.clock=0 I tried this on CURRENT@r191784 (i386) on a Thinkpad T400 (Intel(R) Core(TM)2 Duo CPU T9400) with INVARIANTS, etc. enabled. The result was a panic shortly before /sbin/init is called: panic: lapic1: zero divisor So, the KASSERT in sys/i386/local_apic.c:325 fired: KASSERT(lapic_timer_period != 0, ("lapic%u: zero divisor", lapic_id())); Did I forget something? My /boot/loader.conf: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 kern.hz=100 hint.atrtc.0.clock=0 hint.apic.0.clock=0 hint.ata.2.pm_level=2 hint.ata.3.pm_level=3 vm.pmap.pg_ps_enabled=1 dmesg: http://sites.google.com/site/lwfreebsd/Home/files/dmesg-T400-FreeBSD-CURRENT.txt kernel config: http://sites.google.com/site/lwfreebsd/Home/files/kernel-CURRENT.txt Regards Lucius From mav at FreeBSD.org Mon May 4 22:28:53 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 4 22:28:59 2009 Subject: Fighting for the power. In-Reply-To: <90a5caac0905041119h70101d12i56863e57b27d2e55@mail.gmail.com> References: <49FE1826.4060000@FreeBSD.org> <90a5caac0905041119h70101d12i56863e57b27d2e55@mail.gmail.com> Message-ID: <49FF6C11.5030607@FreeBSD.org> Lucius Windschuh wrote: > I tried this on CURRENT@r191784 (i386) on a Thinkpad T400 (Intel(R) > Core(TM)2 Duo CPU T9400) with INVARIANTS, etc. enabled. > The result was a panic shortly before /sbin/init is called: > > panic: lapic1: zero divisor > > So, the KASSERT in sys/i386/local_apic.c:325 fired: > KASSERT(lapic_timer_period != 0, ("lapic%u: zero divisor", > lapic_id())); > > Did I forget something? > > My /boot/loader.conf: > hint.p4tcc.0.disabled=1 > hint.acpi_throttle.0.disabled=1 > kern.hz=100 > hint.atrtc.0.clock=0 > hint.apic.0.clock=0 > hint.ata.2.pm_level=2 > hint.ata.3.pm_level=3 > vm.pmap.pg_ps_enabled=1 > > dmesg: http://sites.google.com/site/lwfreebsd/Home/files/dmesg-T400-FreeBSD-CURRENT.txt > kernel config: http://sites.google.com/site/lwfreebsd/Home/files/kernel-CURRENT.txt Sorry, my fault. Try attached patch. -- Alexander Motin -------------- next part -------------- --- local_apic.c.prev 2009-05-01 23:53:37.000000000 +0300 +++ local_apic.c 2009-05-05 01:10:04.000000000 +0300 @@ -319,7 +319,7 @@ lapic_setup(int boot) } /* We don't setup the timer during boot on the BSP until later. */ - if (!(boot && PCPU_GET(cpuid) == 0)) { + if (!(boot && PCPU_GET(cpuid) == 0) && lapic_timer_hz != 0) { KASSERT(lapic_timer_period != 0, ("lapic%u: zero divisor", lapic_id())); lapic_timer_set_divisor(lapic_timer_divisor); From lwindschuh at googlemail.com Mon May 4 23:22:14 2009 From: lwindschuh at googlemail.com (Lucius Windschuh) Date: Mon May 4 23:22:26 2009 Subject: Fighting for the power. In-Reply-To: <49FF6C11.5030607@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> <90a5caac0905041119h70101d12i56863e57b27d2e55@mail.gmail.com> <49FF6C11.5030607@FreeBSD.org> Message-ID: <90a5caac0905041622oaddd7cek52f28a9b018b3ea7@mail.gmail.com> 2009/5/5 Alexander Motin : > Lucius Windschuh wrote: >> [...] >> panic: lapic1: zero divisor > [...] > --- local_apic.c.prev ? 2009-05-01 23:53:37.000000000 +0300 > +++ local_apic.c ? ? ? ?2009-05-05 01:10:04.000000000 +0300 > @@ -319,7 +319,7 @@ lapic_setup(int boot) > ? ? ? ?} > > ? ? ? ?/* We don't setup the timer during boot on the BSP until later. */ > - ? ? ? if (!(boot && PCPU_GET(cpuid) == 0)) { > + ? ? ? if (!(boot && PCPU_GET(cpuid) == 0) && lapic_timer_hz != 0) { > ? ? ? ? ? ? ? ?KASSERT(lapic_timer_period != 0, ("lapic%u: zero divisor", > ? ? ? ? ? ? ? ? ? ?lapic_id())); > ? ? ? ? ? ? ? ?lapic_timer_set_divisor(lapic_timer_divisor); This patch solves the panic. C3 instead of C2 saves between 0.5 and 1.5 Watt here with some quick measurements. Thanks. Lucius From peterjeremy at optushome.com.au Tue May 5 09:30:36 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Tue May 5 09:30:42 2009 Subject: Fighting for the power. In-Reply-To: <49FE5EC8.3040205@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> <49FE29A4.30507@root.org> <49FE5EC8.3040205@FreeBSD.org> Message-ID: <20090505091914.GA94521@server.vk2pj.dyndns.org> On 2009-May-04 06:19:36 +0300, Alexander Motin wrote: >System will always have tons of waiting callouts and timeouts to be >handled. So timer will be always needed. Working timer. Yes, but a tickless kernel will let the CPU stay asleep for longer since it doesn't need to wake up just to discover there's nothing to do. >number of idle disk write activity, but I haven't very succeeded. Even >in my quite simple icewm X environment something was persistently >writing something every several minutes. I have found and disabled some >activity sources, but it was not enough. I've recently (in the last few days) worked through minimising the write activity on the SSD in my laptop (I wrote a tool that monitors write transfers via devstat(3) and it would be possible to track down the actual modified files via kqueue(2) if necessary). I'm now down to about two chunks of about 13 transfers each per hour (due to entopy saving and ntp.drift updating). The changes I made were: 1) Mount the SSD filesystems as noatime 2) Turn off all local syslogging (syslog is directed to another system when my laptop is at home, lost otherwise). 3) Change maillog rotation to size instead of daily 4) Run save-entropy once per hour instead of every 11 minutes. 5) Patch the save-entropy script to reduce the write load when it's run (see PR bin/134225). 6) Use a swap-back /tmp By default, ntpd updates ntp.drift every hour. I might do some monitoring and see if the drift changes significantly over time. If it doesn't, hard-wiring the ntp.drift file will save some writes. (The other option would be to tweak the relevant timecounter until the actual drift is 0 and then stop ntpd and just run something like ntpdate regularly to compensate for the remaining drift). Experimentation shows that firefox3 generates a fairly heavy write load - continuously updating several internal databases whilst it is in use. Turning off the "Block reported attack sites" and "Block reported web forgeries" options under 'Security' stops it updating urlclassifier3.sqlite. Note that when you update a file, you implicitly update the associated inode and the filesystem superbock. > What would happen in some >complicated KDE/Gnome environment I am just afraid to think. I'd recommend avoiding a heavyweight window manager and using something like fwvm or vtwm. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090505/6bdcadd5/attachment.pgp From eitanadlerlist at gmail.com Tue May 5 21:55:56 2009 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Tue May 5 21:56:13 2009 Subject: Fighting for the power. In-Reply-To: <20090504011421.GI6901@egr.msu.edu> References: <49FE1826.4060000@FreeBSD.org> <20090504011421.GI6901@egr.msu.edu> Message-ID: <4A00AFEB.7010001@gmail.com> Adam McDougall wrote: > On Mon, May 04, 2009 at 01:18:14AM +0300, Alexander Motin wrote: > > I would like to summarize some of my knowledge on reducing FreeBSD power > consumption and describe some new things I have recently implemented in > 8-CURRENT. The main character of this story is my 12" Acer TravelMate > 6292 laptop with C2D T7700 2.4GHz CPU, 965GM chipset and SATA HDD, under > amd64 8-CURRENT. > Could some of these tips get added to 11.15 Power and Resource Management? I'm sure many people who don't regularly read the mailing lists would like to use these tips. -- Eitan Adler "Security is increased by designing for the way humans actually behave." -Jakob Nielsen From password at dengo.the-gurus.de Thu May 7 00:50:39 2009 From: password at dengo.the-gurus.de (password@dengo.the-gurus.de) Date: Thu May 7 00:50:46 2009 Subject: New -[ dengo's page ]- Password Message-ID: <20090507002810.42396841BD@mx01.d-labs.de> Name: jonnik1 Password: 1agojad5 http://dengo.the-gurus.de/index.php?section=login From imp at bsdimp.com Thu May 7 06:14:20 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Thu May 7 06:14:38 2009 Subject: Fighting for the power. In-Reply-To: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> References: <49FE1826.4060000@FreeBSD.org> <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> Message-ID: <20090507.001059.-1558772981.imp@bsdimp.com> In message: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> "Paul B. Mahol" writes: : On 5/4/09, Alexander Motin wrote: : > 2. PCI devices : > PCI bus provides method to control device power. For example, I have : > completely no use for my FireWire controller and most of time - EHCI USB : > controller. Disabling them allows me to save about 3W of power. To : > disable all unneeded PCI devices you should build kernel without their : > drivers and add to loader.conf: : > hw.pci.do_power_nodriver=3 : > To enable devices back all you need to do is just load their drivers as : > modules. : : Unloading modules doesnt put them back into into D3 state. : You are forced to load some another module again to put wanted device : into D3 state. It should. If it isn't, that's a bug. Warner From onemda at gmail.com Fri May 8 10:34:55 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Fri May 8 10:35:12 2009 Subject: Fighting for the power. In-Reply-To: <20090507.001059.-1558772981.imp@bsdimp.com> References: <49FE1826.4060000@FreeBSD.org> <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> <20090507.001059.-1558772981.imp@bsdimp.com> Message-ID: <3a142e750905080334qb62dcb5hcd07ce028a4ff035@mail.gmail.com> On 5/7/09, M. Warner Losh wrote: > In message: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> > "Paul B. Mahol" writes: > : On 5/4/09, Alexander Motin wrote: > : > 2. PCI devices > : > PCI bus provides method to control device power. For example, I have > : > completely no use for my FireWire controller and most of time - EHCI USB > : > controller. Disabling them allows me to save about 3W of power. To > : > disable all unneeded PCI devices you should build kernel without their > : > drivers and add to loader.conf: > : > hw.pci.do_power_nodriver=3 > : > To enable devices back all you need to do is just load their drivers as > : > modules. > : > : Unloading modules doesnt put them back into into D3 state. > : You are forced to load some another module again to put wanted device > : into D3 state. > > It should. If it isn't, that's a bug. It's a bug. On machine resume(pci_resume), pci_cfg_restore() is called causing D3 -> D0 for all devices(including not attached ones). Unloading module/detaching device doesn't call pci_cfg_save. Should device_detach routine be used or new one like pci_driver_removed() implemented? -- Paul From imp at bsdimp.com Fri May 8 13:10:39 2009 From: imp at bsdimp.com (M. Warner Losh) Date: Fri May 8 13:10:52 2009 Subject: Fighting for the power. In-Reply-To: <3a142e750905080334qb62dcb5hcd07ce028a4ff035@mail.gmail.com> References: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> <20090507.001059.-1558772981.imp@bsdimp.com> <3a142e750905080334qb62dcb5hcd07ce028a4ff035@mail.gmail.com> Message-ID: <20090508.070659.1622573996.imp@bsdimp.com> In message: <3a142e750905080334qb62dcb5hcd07ce028a4ff035@mail.gmail.com> "Paul B. Mahol" writes: : On 5/7/09, M. Warner Losh wrote: : > In message: <3a142e750905040240g58152e69p6fcb797a5e026426@mail.gmail.com> : > "Paul B. Mahol" writes: : > : On 5/4/09, Alexander Motin wrote: : > : > 2. PCI devices : > : > PCI bus provides method to control device power. For example, I have : > : > completely no use for my FireWire controller and most of time - EHCI USB : > : > controller. Disabling them allows me to save about 3W of power. To : > : > disable all unneeded PCI devices you should build kernel without their : > : > drivers and add to loader.conf: : > : > hw.pci.do_power_nodriver=3 : > : > To enable devices back all you need to do is just load their drivers as : > : > modules. : > : : > : Unloading modules doesnt put them back into into D3 state. : > : You are forced to load some another module again to put wanted device : > : into D3 state. : > : > It should. If it isn't, that's a bug. : : It's a bug. : : On machine resume(pci_resume), pci_cfg_restore() is called causing D3 -> D0 for : all devices(including not attached ones). : Unloading module/detaching device doesn't call pci_cfg_save. : : Should device_detach routine be used or new one like : pci_driver_removed() implemented? No. device_detach shouldn't be used for this. This should happen all in the PCI bus code when do_power_nodriver is > 0. Warner From guru at unixarea.de Fri May 8 14:44:04 2009 From: guru at unixarea.de (Matthias Apitz) Date: Fri May 8 14:44:11 2009 Subject: laptop Dell M4400 with -CURRENT? In-Reply-To: <20090428083627.GA3621@rebelion.Sisis.de> References: <20090428083627.GA3621@rebelion.Sisis.de> Message-ID: <20090508141755.GB13584@rebelion.Sisis.de> El d?a Tuesday, April 28, 2009 a las 10:36:27AM +0200, Matthias Apitz escribi?: > > Hello, > > I'm planning to order a new laptop and got an offer for a Dell M4400 > with the following main details: > > Precision M4400 : Intel Core 2 Extreme X9100 (3.06GHz,1066MHz,6MB) > Base Option : 512MB Discrete nVidia FX770M Graphics Card (with 512MB dedicated memory) > Palmrest : UPEK Swipe Fingerprint Reader Biometric > Display : 15.4in Widescreen WUXGA (1920X1200) with Dual CCFL > Camera : Integrated 0.3 Mega Pixel Camera with Microphone for 2CCFL LCD Panel > LCD Back Cover : 2CCFL > Memory : 4096MB (2x2048) 800MHz DDR2 Dual Channel > disk : 250GB Serial ATA (7200 1/min) Festplatte (Free-Fall-Sensor) > Optical Drive : Roxio Creator 9.0 Software and Media Included > Optisches Laufwerk : 8x DVD+/-RW Laufwerk ohne Software > Battery : Primary 9-cell 85 W/HR LI-ION 451-10589 > Battery : Additional 6-Cell 56 W/HR LI-ION 451-10590 > Wireless : EMEA Dell Wireless 1510 (802.11a/b/g/n 2X3) MiniCard for Core 2 Extreme ONLY > Wireless : EMEA Dell Wireless 370 Bluetooth 2.1 MiniCard > Keyboard : Internal German Qwertz Keyboard I have now installed CURRENT in that Precision M4400; shrinked the Vista partition to 50 GByte and installed in the remaining 170 GByte FreeBSD CURRENT from a prepared USB key. It seems that the Quadro FX 770M Graphics Card is not supported by the NVIDIA driver in Xorg 1.6. -- any idea how to solve this? Thx in advance matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From rnoland at FreeBSD.org Fri May 8 16:04:00 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Fri May 8 16:04:07 2009 Subject: laptop Dell M4400 with -CURRENT? In-Reply-To: <20090508141755.GB13584@rebelion.Sisis.de> References: <20090428083627.GA3621@rebelion.Sisis.de> <20090508141755.GB13584@rebelion.Sisis.de> Message-ID: <1241796489.1733.25.camel@balrog.2hip.net> On Fri, 2009-05-08 at 16:17 +0200, Matthias Apitz wrote: > El d?a Tuesday, April 28, 2009 a las 10:36:27AM +0200, Matthias Apitz escribi?: > > > > > Hello, > > > > I'm planning to order a new laptop and got an offer for a Dell M4400 > > with the following main details: > > > > Precision M4400 : Intel Core 2 Extreme X9100 (3.06GHz,1066MHz,6MB) > > Base Option : 512MB Discrete nVidia FX770M Graphics Card (with 512MB dedicated memory) > > Palmrest : UPEK Swipe Fingerprint Reader Biometric > > Display : 15.4in Widescreen WUXGA (1920X1200) with Dual CCFL > > Camera : Integrated 0.3 Mega Pixel Camera with Microphone for 2CCFL LCD Panel > > LCD Back Cover : 2CCFL > > Memory : 4096MB (2x2048) 800MHz DDR2 Dual Channel > > disk : 250GB Serial ATA (7200 1/min) Festplatte (Free-Fall-Sensor) > > Optical Drive : Roxio Creator 9.0 Software and Media Included > > Optisches Laufwerk : 8x DVD+/-RW Laufwerk ohne Software > > Battery : Primary 9-cell 85 W/HR LI-ION 451-10589 > > Battery : Additional 6-Cell 56 W/HR LI-ION 451-10590 > > Wireless : EMEA Dell Wireless 1510 (802.11a/b/g/n 2X3) MiniCard for Core 2 Extreme ONLY > > Wireless : EMEA Dell Wireless 370 Bluetooth 2.1 MiniCard > > Keyboard : Internal German Qwertz Keyboard > > I have now installed CURRENT in that Precision M4400; shrinked the Vista > partition to 50 GByte and installed in the remaining 170 GByte FreeBSD > CURRENT from a prepared USB key. > > It seems that the Quadro FX 770M Graphics Card is not supported by the > NVIDIA driver in Xorg 1.6. -- any idea how to solve this? I have ported the nouveau drm driver. http://people.freebsd.org/~rnoland/drm-nouveau-043009.patch It is working on NV50 cards, NV40 was working, but with WITNESS enabled I seem to be getting a panic on NV40. My NV40 card seems to be having memory issues so I haven't been able to get and/or see the backtrace. I think it is just a locking issue which should be pretty easily solved if I can get a clear backtrace. You will need current libdrm and xf86-video-nouveau from ports. This won't get you 3d right now, but should get you EXA + Xv. robert. > Thx in advance > > matthias -- Robert Noland FreeBSD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090508/cab440e6/attachment.pgp From freetex at msn.com Sun May 10 10:48:11 2009 From: freetex at msn.com (freetex@msn.com) Date: Sun May 10 10:48:18 2009 Subject: Thank you for signing our guestbook Message-ID: <20090510102128.27132.qmail@leo.dns-shield.com> Thank you for signing our guestbook! Please visit us again at www.SandersQuarterHorses.com From kientzle at freebsd.org Mon May 11 06:14:00 2009 From: kientzle at freebsd.org (Tim Kientzle) Date: Mon May 11 06:14:07 2009 Subject: Fighting for the power. In-Reply-To: <49FE1826.4060000@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> Message-ID: <4A07BC4D.7080604@freebsd.org> Alexander Motin wrote: > I would like to summarize some of my knowledge on reducing FreeBSD power > consumption and describe some new things I have recently implemented in > 8-CURRENT. ... This is great work! > - C3 state allows CPU completely stop all internal clocks, reduce > voltage and disconnect from system bus. This state gives additional > power saving effect, but .... local APIC timers in > each CPU core, used by FreeBSD as event sources on SMP, are not > functioning. ... Originally, before SMP era, FreeBSD used i8254 (for HZ) > and RTC (for stats) chipset timers. I have made changes to 8-CURRENT to > resurrect them for SMP systems. To use them, you can disable local APIC > timers by adding to /boot/loader.conf: > hint.apic.0.clock=0 I experimented a little bit with this and had a few odd experiences: sysctl hw.acpi.cpu.cx_lowest=C3 did drop power consumption significantly but made the system pretty unresponsive. In particular, the system completely hung at shutdown. I presume the hang was the APIC timer problem you mentioned. I started to try the "hint.apic.0.clock", but noticed in your commit r191720: > Add hint.apic.0.clock tunable. Setting it 0 disables using > LAPIC timers as hard-/stat-/profclock sources falling back > to using i8254 and rtc timers. > ... > This technique is not working for SMP yet, as only one CPU > receives timer interrupts. But I think that problem could > be fixed by forwarding interrupts to other CPUs with IPI. Is anyone looking at this yet? Tim From guru at unixarea.de Mon May 11 12:21:27 2009 From: guru at unixarea.de (Matthias Apitz) Date: Mon May 11 12:21:36 2009 Subject: laptop Dell M4400 with -CURRENT? In-Reply-To: <1241796489.1733.25.camel@balrog.2hip.net> References: <20090428083627.GA3621@rebelion.Sisis.de> <20090508141755.GB13584@rebelion.Sisis.de> <1241796489.1733.25.camel@balrog.2hip.net> Message-ID: <20090511122121.GA9961@rebelion.Sisis.de> El d?a Friday, May 08, 2009 a las 10:28:09AM -0500, Robert Noland escribi?: > I have ported the nouveau drm driver. > > http://people.freebsd.org/~rnoland/drm-nouveau-043009.patch > > It is working on NV50 cards, NV40 was working, but with WITNESS enabled > I seem to be getting a panic on NV40. My NV40 card seems to be having > memory issues so I haven't been able to get and/or see the backtrace. I > think it is just a locking issue which should be pretty easily solved if > I can get a clear backtrace. > > You will need current libdrm and xf86-video-nouveau from ports. > > This won't get you 3d right now, but should get you EXA + Xv. Hello Robert, I have applied your patch and ported xf86-video-nouveau from ports; all is fine now and the display comes up with 1920x1200 resolution; I'm attaching Xorg.0.log so you can see what kind of chips the nouveau driver is detecting. Thanks again for your work and help matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. -------------- next part -------------- X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-CURRENT i386 Current Operating System: FreeBSD current 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Mon May 11 13:31:04 UTC 2009 guru@current:/usr/obj/usr/src/sys/REBELION-CURRENT i386 Build Date: 28 April 2009 11:44:04AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 11 14:07:21 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "AllowEmptyInput" "false" (==) Automatically adding devices (==) Automatically enabling devices (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, built-ins (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x6a0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0@1:0:0) nVidia Corporation Quadro FX 770M rev 161, Mem @ 0xf5000000/16777216, 0xe0000000/268435456, 0xf2000000/33554432, I/O @ 0x0000df00/128, BIOS @ 0x????????/65536 (II) System resource ranges: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) "dri2" will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: "nouveau" (II) Loading /usr/local/lib/xorg/modules/drivers//nouveau_drv.so (II) Module nouveau: vendor="X.Org Foundation" compiled for 1.6.0, module version = 0.0.10 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) LoadModule: "mouse" (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (II) LoadModule: "kbd" (II) Loading /usr/local/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.3.2 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (II) NOUVEAU driver 20090408.d8545e6 (II) NOUVEAU driver for NVIDIA chipset families : RIVA TNT (NV04) RIVA TNT2 (NV05) GeForce 256 (NV10) GeForce 2 (NV11, NV15) GeForce 4MX (NV17, NV18) GeForce 3 (NV20) GeForce 4Ti (NV25, NV28) GeForce FX (NV3x) GeForce 6 (NV4x) GeForce 7 (G7x) GeForce 8 (G8x) (II) Primary Device is: PCI 01@00:00:0 (II) resource ranges after probing: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (--) NOUVEAU(0): Chipset: "NVIDIA NV96" (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 5.0 (II) NOUVEAU(0): Initializing int10 (==) NOUVEAU(0): Write-combining range (0xa0000,0x20000) was already clear (==) NOUVEAU(0): Write-combining range (0xc0000,0x40000) was already clear (II) NOUVEAU(0): Primary V_BIOS segment is: 0xc000 (==) NOUVEAU(0): Write-combining range (0x0,0x1000) was already clear (II) Loading sub module "dri" (II) LoadModule: "dri" (II) Reloading /usr/local/lib/xorg/modules/extensions//libdri.so (II) NOUVEAU(0): Loaded DRI module drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) drmOpenByBusid: drmOpenMinor returns 10 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 (II) [drm] loaded kernel module for "nouveau" driver. (II) [drm] DRM interface version 1.2 (II) [drm] DRM open master succeeded. (II) NOUVEAU(0): [drm] nouveau interface version: 0.0.12 (--) NOUVEAU(0): [drm] kernel modesetting not available (--) NOUVEAU(0): VESA-HACK: Console VGA mode is 0x3 (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32 (==) NOUVEAU(0): RGB weight 888 (==) NOUVEAU(0): Default visual is TrueColor (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/local/lib/xorg/modules//libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.6.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 5.0 (==) NOUVEAU(0): Randr1.2 support enabled (==) NOUVEAU(0): Using HW cursor (--) NOUVEAU(0): Linear framebuffer at 0xE0000000 (--) NOUVEAU(0): MMIO registers at 0xF5000000 (II) NOUVEAU(0): Initial CRTC_OWNER is 0 (II) NOUVEAU(0): Attempting to load BIOS image from PROM (!!) NOUVEAU(0): ... BIOS signature not found (II) NOUVEAU(0): Attempting to load BIOS image from PRAMIN (II) NOUVEAU(0): ... appears to be valid (II) NOUVEAU(0): BIT BIOS found (II) NOUVEAU(0): Bios version 62.94.34.00 (WW) NOUVEAU(0): TMDS table revision 2.0 not currently supported (II) NOUVEAU(0): Found Display Configuration Block version 4.0 (!!) NOUVEAU(0): Raw DCB entry 0: 01000323 00010034 (WW) NOUVEAU(0): G80+ LVDS not initialized by driver; ignoring conf bits (!!) NOUVEAU(0): Raw DCB entry 1: 02011300 00000028 (!!) NOUVEAU(0): Raw DCB entry 2: 02022386 0f200010 (WW) NOUVEAU(0): DCB I2C table has port type 6 (!!) NOUVEAU(0): Raw DCB entry 3: 02022332 00020010 (!!) NOUVEAU(0): Raw DCB entry 4: 040333a6 0f200010 (WW) NOUVEAU(0): DCB I2C table has port type 6 (!!) NOUVEAU(0): Raw DCB entry 5: 04033312 00020010 (--) NOUVEAU(0): Parsing VBIOS init table 0 at offset 0xD1CE (EE) NOUVEAU(0): ========== unknown reg 0x00021220 ========== (EE) NOUVEAU(0): ========== unknown reg 0x0002121C ========== (EE) NOUVEAU(0): 0xD2D6: Init table command not found: 0x97 (--) NOUVEAU(0): Parsing VBIOS init table 1 at offset 0xD5D6 (--) NOUVEAU(0): Parsing VBIOS init table 2 at offset 0xE59F (--) NOUVEAU(0): Parsing VBIOS init table 3 at offset 0xE6E8 (--) NOUVEAU(0): Parsing VBIOS init table 4 at offset 0xE924 (II) NOUVEAU(0): LVDS clock seems to be 151700 KHz. (II) NOUVEAU(0): Found 0 modes, this is not useful (II) NOUVEAU(0): NV50DispPreInit is called. (--) NOUVEAU(0): DCB entry 0: type: 3, i2c_index: 2, heads: 3, bus: 0, or: 1 (II) NOUVEAU(0): I2C bus "LVDS-0" initialized. (II) NOUVEAU(0): SOR-0 attached with index 0 to LVDS-0 (--) NOUVEAU(0): DCB entry 1: type: 0, i2c_index: 0, heads: 3, bus: 1, or: 2 (II) NOUVEAU(0): I2C bus "VGA-0" initialized. (II) NOUVEAU(0): DAC-1 attached with index 0 to VGA-0 (--) NOUVEAU(0): DCB entry 2: type: 6, i2c_index: 8, heads: 3, bus: 2, or: 2 (WW) NOUVEAU(0): DCB type 6 not known (--) NOUVEAU(0): DCB entry 3: type: 2, i2c_index: 3, heads: 3, bus: 2, or: 2 (II) NOUVEAU(0): I2C bus "DVI-0" initialized. (II) NOUVEAU(0): SOR-1 attached with index 0 to DVI-0 (--) NOUVEAU(0): DCB entry 4: type: 6, i2c_index: 10, heads: 3, bus: 3, or: 4 (WW) NOUVEAU(0): DCB type 6 not known (--) NOUVEAU(0): DCB entry 5: type: 2, i2c_index: 1, heads: 3, bus: 3, or: 4 (II) NOUVEAU(0): I2C bus "DVI-1" initialized. (II) NOUVEAU(0): SOR-2 attached with index 0 to DVI-1 (II) NOUVEAU(0): Output LVDS-0 using monitor section Monitor0 (II) NOUVEAU(0): Output VGA-0 has no monitor section (II) NOUVEAU(0): Output DVI-0 has no monitor section (II) NOUVEAU(0): Output DVI-1 has no monitor section (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): I2C device "LVDS-0:E-EDID segment register" registered at address 0x60. (II) NOUVEAU(0): I2C device "LVDS-0:ddc2" registered at address 0xA0. (II) NOUVEAU(0): Detected a Digital output on LVDS-0 (II) NOUVEAU(0): Found a suitable output, index 0 (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): EDID vendor "LGD", prod id 399 (II) NOUVEAU(0): Printing DDC gathered Modelines: (II) NOUVEAU(0): Modeline "1920x1200"x0.0 151.70 1920 1950 1980 2014 1200 1203 1209 1256 +hsync -vsync (75.3 kHz) (II) NOUVEAU(0): Modeline "1920x1200"x0.0 151.70 1920 1950 1980 2014 1200 1203 1209 1884 -hsync -vsync (75.3 kHz) (II) NOUVEAU(0): NV50ConnectorGetDDCModes is called. (II) NOUVEAU(0): EDID vendor "LGD", prod id 399 (II) NOUVEAU(0): LVDS-0: preferred mode is 1920x1200 (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): I2C device "VGA-0:E-EDID segment register" registered at address 0x60. (II) NOUVEAU(0): I2C device "VGA-0:ddc2" registered at address 0xA0. (II) NOUVEAU(0): Using bios provided load value of 506 (--) NOUVEAU(0): No Load present on DAC-1 (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): I2C device "DVI-0:E-EDID segment register" registered at address 0x60. (II) NOUVEAU(0): I2C device "DVI-0:ddc2" registered at address 0xA0. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): I2C device "DVI-1:E-EDID segment register" registered at address 0x60. (II) NOUVEAU(0): I2C device "DVI-1:ddc2" registered at address 0xA0. (II) NOUVEAU(0): Output LVDS-0 connected (II) NOUVEAU(0): Output VGA-0 disconnected (II) NOUVEAU(0): Output DVI-0 disconnected (II) NOUVEAU(0): Output DVI-1 disconnected (II) NOUVEAU(0): Using exact sizes for initial modes (II) NOUVEAU(0): Output LVDS-0 using initial mode 1920x1200 (--) NOUVEAU(0): VideoRAM: 262144 kBytes (==) NOUVEAU(0): Using gamma correction (1.0, 1.0, 1.0) (--) NOUVEAU(0): Virtual size is 1920x1920 (pitch 1920) (**) NOUVEAU(0): Driver mode "1920x1200": 151.7 MHz (scaled from 0.0 MHz), 75.3 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "1920x1200"x60.0 151.70 1920 1950 1980 2014 1200 1203 1209 1256 +hsync -vsync (75.3 kHz) (**) NOUVEAU(0): Driver mode "1920x1200": 151.7 MHz (scaled from 0.0 MHz), 75.3 kHz, 40.0 Hz (II) NOUVEAU(0): Modeline "1920x1200"x40.0 151.70 1920 1950 1980 2014 1200 1203 1209 1884 -hsync -vsync (75.3 kHz) (**) NOUVEAU(0): Default mode "1600x1200": 229.5 MHz (scaled from 0.0 MHz), 106.2 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "1600x1200"x85.0 229.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (106.2 kHz) (**) NOUVEAU(0): Default mode "1600x1200": 202.5 MHz (scaled from 0.0 MHz), 93.8 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "1600x1200"x75.0 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (93.8 kHz) (**) NOUVEAU(0): Default mode "1600x1200": 189.0 MHz (scaled from 0.0 MHz), 87.5 kHz, 70.0 Hz (II) NOUVEAU(0): Modeline "1600x1200"x70.0 189.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (87.5 kHz) (**) NOUVEAU(0): Default mode "1600x1200": 175.5 MHz (scaled from 0.0 MHz), 81.2 kHz, 65.0 Hz (II) NOUVEAU(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz) (**) NOUVEAU(0): Default mode "1600x1200": 162.0 MHz (scaled from 0.0 MHz), 75.0 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz) (**) NOUVEAU(0): Default mode "1400x1050": 155.8 MHz (scaled from 0.0 MHz), 81.5 kHz, 74.8 Hz (II) NOUVEAU(0): Modeline "1400x1050"x74.8 155.80 1400 1464 1784 1912 1050 1052 1064 1090 +hsync +vsync (81.5 kHz) (**) NOUVEAU(0): Default mode "1400x1050": 122.0 MHz (scaled from 0.0 MHz), 64.9 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz) (**) NOUVEAU(0): Default mode "1280x1024": 157.5 MHz (scaled from 0.0 MHz), 91.1 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "1280x1024"x85.0 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync (91.1 kHz) (**) NOUVEAU(0): Default mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz) (**) NOUVEAU(0): Default mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz) (**) NOUVEAU(0): Default mode "1280x960": 148.5 MHz (scaled from 0.0 MHz), 85.9 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "1280x960"x85.0 148.50 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync (85.9 kHz) (**) NOUVEAU(0): Default mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz) (**) NOUVEAU(0): Default mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz) (**) NOUVEAU(0): Default mode "1024x768": 94.5 MHz (scaled from 0.0 MHz), 68.7 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz) (**) NOUVEAU(0): Default mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.0 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz) (**) NOUVEAU(0): Default mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz) (**) NOUVEAU(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (**) NOUVEAU(0): Default mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz) (**) NOUVEAU(0): Default mode "800x600": 56.3 MHz (scaled from 0.0 MHz), 53.7 kHz, 85.1 Hz (II) NOUVEAU(0): Modeline "800x600"x85.1 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz) (**) NOUVEAU(0): Default mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz) (**) NOUVEAU(0): Default mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz) (**) NOUVEAU(0): Default mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (**) NOUVEAU(0): Default mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) (**) NOUVEAU(0): Default mode "640x480": 36.0 MHz (scaled from 0.0 MHz), 43.3 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz) (**) NOUVEAU(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz) (**) NOUVEAU(0): Default mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz) (**) NOUVEAU(0): Default mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (**) NOUVEAU(0): Default mode "720x400": 35.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.0 Hz (II) NOUVEAU(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (37.9 kHz) (**) NOUVEAU(0): Default mode "640x400": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.1 Hz (II) NOUVEAU(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz) (**) NOUVEAU(0): Default mode "640x350": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 85.1 Hz (II) NOUVEAU(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz) (**) NOUVEAU(0): Display dimensions: (330, 210) mm (**) NOUVEAU(0): DPI set to (147, 232) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (II) Loading sub module "exa" (II) LoadModule: "exa" (II) Loading /usr/local/lib/xorg/modules//libexa.so (II) Module exa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.4.0 ABI class: X.Org Video Driver, version 5.0 (II) Loading sub module "shadowfb" (II) LoadModule: "shadowfb" (II) Loading /usr/local/lib/xorg/modules//libshadowfb.so (II) Module shadowfb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (==) NOUVEAU(0): Write-combining range (0xa0000,0x10000) was already clear (II) NOUVEAU(0): Allocated 128MiB VRAM for framebuffer + offscreen pixmaps, at offset 0x20000000 (II) NOUVEAU(0): AGPGART: 32MiB available (II) NOUVEAU(0): GART: Allocated 16MiB as a scratch buffer (II) NOUVEAU(0): [drm] Using the DRM lock SAREA also for drawables. (II) NOUVEAU(0): [drm] framebuffer handle = 0xe0000000 (II) NOUVEAU(0): [drm] added 1 reserved context for kernel (II) NOUVEAU(0): X context handle = 0x1 (II) NOUVEAU(0): [drm] installed DRM signal handler (II) NOUVEAU(0): Opened GPU channel 2 (II) EXA(0): Offscreen pixmap area of 119472128 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) Composite (RENDER acceleration) (II) UploadToScreen (II) DownloadFromScreen (==) NOUVEAU(0): Backing store disabled (==) NOUVEAU(0): Silken mouse enabled (II) NOUVEAU(0): [DRI] installation complete (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video. (II) NOUVEAU(0): [XvMC] Extension initialized. (II) NOUVEAU(0): NVEnterVT is called. (II) NOUVEAU(0): NV50DispInit is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50DacGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50DacSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50DacGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_crtc_dpms is called with mode 3 for CRTC0. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50DacGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_crtc_dpms is called with mode 3 for CRTC1. (II) NOUVEAU(0): nv50_output_prepare is called. (II) NOUVEAU(0): nv50_crtc_prepare is called for CRTC0. (II) NOUVEAU(0): NV50DacModeSet is called. (II) NOUVEAU(0): Disconnecting DAC. (II) NOUVEAU(0): NV50SorModeSet is called. (II) NOUVEAU(0): Disconnecting SOR. (II) NOUVEAU(0): NV50SorModeSet is called. (II) NOUVEAU(0): Disconnecting SOR. (II) NOUVEAU(0): nv50_crtc_mode_set is called for CRTC0. (II) NOUVEAU(0): NV50CrtcModeSet is called for CRTC0. (II) NOUVEAU(0): NV50CrtcSetDither is called (no update). (II) NOUVEAU(0): NV50CrtcBlank is called (unblanked) for CRTC0. (II) NOUVEAU(0): nv50_output_mode_set is called. (II) NOUVEAU(0): NV50SorModeSet is called. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 0. (II) NOUVEAU(0): NV50CrtcSetScale is called with mode 2 for CRTC0. (II) NOUVEAU(0): nv50_crtc_commit is called for CRTC0. (II) NOUVEAU(0): NV50CrtcBlank is called (blanked) for CRTC1. (II) NOUVEAU(0): NV50CrtcSetPixelClock is called for CRTC0. (II) NOUVEAU(0): NV50CrtcSetClockMode is called for CRTC0. (II) NOUVEAU(0): nv50_output_commit is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50DacSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_crtc_dpms is called with mode 3 for CRTC1. (II) NOUVEAU(0): DPMS enabled (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC0. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC0. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC1. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC1. (--) RandR disabled (II) Initializing built-in extension Generic Event Extension (II) Initializing built-in extension SHAPE (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension BIG-REQUESTS (II) Initializing built-in extension SYNC (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-MISC (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 (II) NOUVEAU(0): Setting screen physical size to 331 x 207 (**) Option "Protocol" "auto" (**) Mouse0: Device: "/dev/sysmouse" (**) Mouse0: Protocol: "auto" (**) Option "CorePointer" (**) Mouse0: always reports core events (**) Option "Device" "/dev/sysmouse" (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5 6 7" (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7 (**) Mouse0: Buttons: 11 (**) Mouse0: Sensitivity: 1 (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (**) Mouse0: (accel) keeping acceleration scheme 1 (**) Mouse0: (accel) filter chain progression: 2.00 (**) Mouse0: (accel) filter stage 0: 20.00 ms (**) Mouse0: (accel) set acceleration profile 0 (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse (**) Option "CoreKeyboard" (**) Keyboard0: always reports core events (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) exaCopyDirty: Pending damage region empty! (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): Detected a Digital output on LVDS-0 (II) NOUVEAU(0): Found a suitable output, index 0 (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): EDID vendor "LGD", prod id 399 (II) NOUVEAU(0): Printing DDC gathered Modelines: (II) NOUVEAU(0): Modeline "1920x1200"x0.0 151.70 1920 1950 1980 2014 1200 1203 1209 1256 +hsync -vsync (75.3 kHz) (II) NOUVEAU(0): Modeline "1920x1200"x0.0 151.70 1920 1950 1980 2014 1200 1203 1209 1884 -hsync -vsync (75.3 kHz) (II) NOUVEAU(0): NV50ConnectorGetDDCModes is called. (II) NOUVEAU(0): EDID vendor "LGD", prod id 399 (II) NOUVEAU(0): LVDS-0: preferred mode is 1920x1200 (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): Using bios provided load value of 506 (--) NOUVEAU(0): No Load present on DAC-1 (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): Detected a Digital output on LVDS-0 (II) NOUVEAU(0): Found a suitable output, index 0 (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): EDID vendor "LGD", prod id 399 (II) NOUVEAU(0): Printing DDC gathered Modelines: (II) NOUVEAU(0): Modeline "1920x1200"x0.0 151.70 1920 1950 1980 2014 1200 1203 1209 1256 +hsync -vsync (75.3 kHz) (II) NOUVEAU(0): Modeline "1920x1200"x0.0 151.70 1920 1950 1980 2014 1200 1203 1209 1884 -hsync -vsync (75.3 kHz) (II) NOUVEAU(0): NV50ConnectorGetDDCModes is called. (II) NOUVEAU(0): EDID vendor "LGD", prod id 399 (II) NOUVEAU(0): LVDS-0: preferred mode is 1920x1200 (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_mode_valid is called. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): Using bios provided load value of 506 (--) NOUVEAU(0): No Load present on DAC-1 (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): nv50_output_detect is called. (II) NOUVEAU(0): NV50ConnectorDDCDetect is called. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC0. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC0. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC1. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC1. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC0. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC0. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC1. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC1. (II) NOUVEAU(0): NVLeaveVT is called. (II) NOUVEAU(0): NV50DispShutdown is called. (II) NOUVEAU(0): NV50CrtcBlank is called (blanked) for CRTC0. (II) NOUVEAU(0): NV50CrtcBlank is called (blanked) for CRTC1. (II) NOUVEAU(0): NVEnterVT is called. (II) NOUVEAU(0): NV50DispInit is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50DacGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50DacSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50DacGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_crtc_dpms is called with mode 3 for CRTC0. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50DacGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_output_get_crtc is called. (II) NOUVEAU(0): NV50SorGetCurrentCrtc is called. (II) NOUVEAU(0): nv50_crtc_dpms is called with mode 3 for CRTC1. (II) NOUVEAU(0): nv50_output_prepare is called. (II) NOUVEAU(0): nv50_crtc_prepare is called for CRTC0. (II) NOUVEAU(0): NV50DacModeSet is called. (II) NOUVEAU(0): Disconnecting DAC. (II) NOUVEAU(0): NV50SorModeSet is called. (II) NOUVEAU(0): Disconnecting SOR. (II) NOUVEAU(0): NV50SorModeSet is called. (II) NOUVEAU(0): Disconnecting SOR. (II) NOUVEAU(0): nv50_crtc_mode_set is called for CRTC0. (II) NOUVEAU(0): NV50CrtcModeSet is called for CRTC0. (II) NOUVEAU(0): NV50CrtcSetDither is called (no update). (II) NOUVEAU(0): NV50CrtcBlank is called (unblanked) for CRTC0. (II) NOUVEAU(0): nv50_output_mode_set is called. (II) NOUVEAU(0): NV50SorModeSet is called. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 0. (II) NOUVEAU(0): NV50CrtcSetScale is called with mode 2 for CRTC0. (II) NOUVEAU(0): nv50_crtc_commit is called for CRTC0. (II) NOUVEAU(0): NV50CrtcBlank is called (blanked) for CRTC1. (II) NOUVEAU(0): NV50CrtcSetPixelClock is called for CRTC0. (II) NOUVEAU(0): NV50CrtcSetClockMode is called for CRTC0. (II) NOUVEAU(0): nv50_output_commit is called. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50DacSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_output_dpms is called with mode 3. (II) NOUVEAU(0): NV50SorSetPowerMode is called with mode 3. (II) NOUVEAU(0): nv50_crtc_dpms is called with mode 3 for CRTC1. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC0. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC0. (II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC1. (II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC1. (**) Option "BaudRate" "1200" (**) Option "StopBits" "2" (**) Option "DataBits" "8" (**) Option "Parity" "None" (**) Option "Vmin" "1" (**) Option "Vtime" "0" (**) Option "FlowControl" "None" From mav at FreeBSD.org Mon May 11 12:22:11 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 11 12:22:23 2009 Subject: Fighting for the power. In-Reply-To: <4A07BC4D.7080604@freebsd.org> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> Message-ID: <4A081868.6010906@FreeBSD.org> Tim Kientzle wrote: > I started to try the "hint.apic.0.clock", but noticed > in your commit r191720: > Alexander Motin wrote: >> Add hint.apic.0.clock tunable. Setting it 0 disables using >> LAPIC timers as hard-/stat-/profclock sources falling back >> to using i8254 and rtc timers. >> ... >> This technique is not working for SMP yet, as only one CPU >> receives timer interrupts. But I think that problem could >> be fixed by forwarding interrupts to other CPUs with IPI. > > Is anyone looking at this yet? I have implemented SMP support for i386 and amd64 in some of my later commits. -- Alexander Motin From onemda at gmail.com Mon May 11 20:08:51 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon May 11 20:08:57 2009 Subject: Fighting for the power. In-Reply-To: <4A081868.6010906@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> Message-ID: <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> On 5/11/09, Alexander Motin wrote: > Tim Kientzle wrote: >> I started to try the "hint.apic.0.clock", but noticed >> in your commit r191720: >> Alexander Motin wrote: >>> Add hint.apic.0.clock tunable. Setting it 0 disables using >>> LAPIC timers as hard-/stat-/profclock sources falling back >>> to using i8254 and rtc timers. >>> ... >>> This technique is not working for SMP yet, as only one CPU >>> receives timer interrupts. But I think that problem could >>> be fixed by forwarding interrupts to other CPUs with IPI. >> >> Is anyone looking at this yet? > > I have implemented SMP support for i386 and amd64 in some of my later > commits. And all those hacks helps verry little in my case, most gain I get when laptop monitor is switched off. Even switching hard disk off improves battery life very little. interrupt total rate irq1: atkbd0 5206 3 irq0: clk 156008 99 irq9: acpi0 1152 0 irq12: psm0 16092 10 irq14: ata0 6587 4 irq15: ata1 1 0 irq17: ndis0 28646 18 irq256: hdac0 18 0 Total 213710 136 -- Paul From mav at FreeBSD.org Mon May 11 23:13:39 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Mon May 11 23:13:52 2009 Subject: Fighting for the power. In-Reply-To: <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> Message-ID: <4A08B10E.4040702@FreeBSD.org> Paul B. Mahol wrote: > On 5/11/09, Alexander Motin wrote: >> Tim Kientzle wrote: >>> I started to try the "hint.apic.0.clock", but noticed >>> in your commit r191720: >>> Alexander Motin wrote: >>>> Add hint.apic.0.clock tunable. Setting it 0 disables using >>>> LAPIC timers as hard-/stat-/profclock sources falling back >>>> to using i8254 and rtc timers. >>>> ... >>>> This technique is not working for SMP yet, as only one CPU >>>> receives timer interrupts. But I think that problem could >>>> be fixed by forwarding interrupts to other CPUs with IPI. >>> Is anyone looking at this yet? >> I have implemented SMP support for i386 and amd64 in some of my later >> commits. > > And all those hacks helps verry little in my case, most gain I get when > laptop monitor is switched off. Even switching hard disk off improves battery > life very little. Monitor is surely one of major power consumers, but there are not so much things which you can do about it, as without power there will be no backlight. All you can do is tune backlight to minimum level required in every specific situation. What's about general effect, the main idea here is the same as in audio processing: result mostly depends on quality of the worst component. Your system may just have some other consumers which I don't have. For example, desktop CPU instead of mobile, desktop chipset instead of mobile, powerful external video instead of (or even in addition to) built-in, and so on. -- Alexander Motin From knowtree at aloha.com Tue May 12 07:38:15 2009 From: knowtree at aloha.com (Gary Dunn) Date: Tue May 12 07:38:27 2009 Subject: Fighting for the power. In-Reply-To: <4A08B10E.4040702@FreeBSD.org> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> <4A08B10E.4040702@FreeBSD.org> Message-ID: <1242110455.2664.9.camel@slate01> On Tue, 2009-05-12 at 02:13 +0300, Alexander Motin wrote: ... > > What's about general effect, the main idea here is the same as in audio > processing: result mostly depends on quality of the worst component. > Your system may just have some other consumers which I don't have. For > example, desktop CPU instead of mobile, desktop chipset instead of > mobile, powerful external video instead of (or even in addition to) > built-in, and so on. > Interesting point. Is there a power consumption benchmark for evaluating hardware for use with FreeBSD? -- Gary Dunn, Honolulu osp@aloha.com http://openslate.net/ http://e9erust.blogspot.com/ Sent from Slate001 From smithi at nimnet.asn.au Tue May 12 10:53:24 2009 From: smithi at nimnet.asn.au (Ian Smith) Date: Tue May 12 10:53:31 2009 Subject: Fighting for the power. In-Reply-To: <1242110455.2664.9.camel@slate01> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> <4A08B10E.4040702@FreeBSD.org> <1242110455.2664.9.camel@slate01> Message-ID: <20090512182420.K46325@sola.nimnet.asn.au> On Mon, 11 May 2009, Gary Dunn wrote: > On Tue, 2009-05-12 at 02:13 +0300, Alexander Motin wrote: > ... > > > > What's about general effect, the main idea here is the same as in audio > > processing: result mostly depends on quality of the worst component. > > Your system may just have some other consumers which I don't have. For > > example, desktop CPU instead of mobile, desktop chipset instead of > > mobile, powerful external video instead of (or even in addition to) > > built-in, and so on. > > > > Interesting point. Is there a power consumption benchmark for evaluating > hardware for use with FreeBSD? make buildworld, running on battery? :-) More seriously: thanks to Nate's earlier niggling, I've been thinking towards a richer set of power profiles than our {performance,economy} dichotomy for a while, both in terms of various different work/play and AC/battery scenarious, and re specific settings that may be more or less optimal for particular hardware, that could be distributed or advised as more of a basic working set rather than as a series of 'try this' hints. Many of the useful points Alexander makes apply to lots of recent kit, but perhaps not as applicably to some older machines - just one example being whether using C3 is likely to help or hinder, eg with the C3 quirks for (some) PIIX4 chipset variants that got some work last? year. I'm not a C programmer, so I've been thinking more towards inclusion as a deeper level of rc.conf variables and parsing of these by sh script, tweaking sysctls after the fashion of the present power_profile and its triggering by devd events. Some features of individual machine / scenario profiles could include min/max cpu freq settings, whether or not to use p4tcc/acpi_throttle, highest C-state, powerd high/low load shift up/down percentages, and perhaps whether or not to power-down (D3) various devices/subsystems .. Recent exposure to (debian etch) cpufreqd profiles provides a few more ideas, eg here are a few examples from its default cpufreqd.conf, noting that cpufreqd and friends are add-ons, not system components, in debian. # stay in performance mode for the first minutes [Rule] name=AC Off - High Power ac=off # (on/off) battery_interval=70-100 #exec_post=echo 5 > /proc/acpi/sony/brightness profile=Performance Low [/Rule] # conservative mode when not AC [Rule] name=AC Off - Medium Battery ac=off # (on/off) battery_interval=30-70 #exec_post=echo 3 > /proc/acpi/sony/brightness profile=Powersave High [/Rule] # conservative mode when not AC [Rule] name=AC Off - Low Battery ac=off # (on/off) battery_interval=0-30 #exec_post=echo 3 > /proc/acpi/sony/brightness profile=Powersave Low [/Rule] ## # Special Rules ## # CPU Too hot! [Rule] name=CPU Too Hot acpi_temperature=55-100 cpu_interval=50-100 profile=Performance Low [/Rule] # use performance mode if I'm watching a movie # I don't care for batteries! # But don't heat too much. [Rule] name=Movie Watcher programs=xine,mplayer,gmplayer battery_interval=0-100 acpi_temperature=0-60 cpu_interval=0-100 profile=Performance High [/Rule] cheers, Ian From mav at FreeBSD.org Tue May 12 11:45:14 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Tue May 12 11:45:30 2009 Subject: Fighting for the power. In-Reply-To: <1242110455.2664.9.camel@slate01> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> <4A08B10E.4040702@FreeBSD.org> <1242110455.2664.9.camel@slate01> Message-ID: <4A096131.4040405@FreeBSD.org> Gary Dunn wrote: > On Tue, 2009-05-12 at 02:13 +0300, Alexander Motin wrote: > ... >> What's about general effect, the main idea here is the same as in audio >> processing: result mostly depends on quality of the worst component. >> Your system may just have some other consumers which I don't have. For >> example, desktop CPU instead of mobile, desktop chipset instead of >> mobile, powerful external video instead of (or even in addition to) >> built-in, and so on. > > Interesting point. Is there a power consumption benchmark for evaluating > hardware for use with FreeBSD? It is difficult to speak about benchmark, as soon as we are talking about idle power. I think the first step evaluation could be made with vendor provided data, as it mostly depends on hardware. If vendor speaks about 2 hours on battery, then there is quite small probability to get much out of that system, as it looks mostly positioned as desktop and may have many desktop components. And opposite, system declaring 9 hours must support a lot of different power-saving technologies to reach it. -- Alexander Motin From dan at langille.org Tue May 12 20:33:35 2009 From: dan at langille.org (Dan Langille) Date: Tue May 12 20:33:41 2009 Subject: EeePC 1000HE + ath on 7.2-RELEASE Message-ID: <4A09D884.8050309@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to get my Atheros Wireless LAN running on my mother's 1000HE. The NIC runs on current, but we cannot get the USB-serial cable to work properly. So we are on 7.2-RELEASE now. Reading http://wiki.freebsd.org/AsusEee, under 'Atheros Wireless LAN', I see references to downloading sys/contrib/dev/ath I have no such directory in my checkout of HEAD, but I do have this (note, no contrib directory in the path): [dan@laptop:~/tmp/HEAD/src/sys/dev/ath] $ ls -l total 312 - -rw-r--r-- 1 dan dan 10033 May 7 20:23 ah_osdep.c - -rw-r--r-- 1 dan dan 5152 May 7 20:23 ah_osdep.h drwxr-xr-x 7 dan dan 512 May 12 10:25 ath_hal drwxr-xr-x 5 dan dan 512 May 12 10:25 ath_rate - -rw-r--r-- 1 dan dan 214289 May 6 20:35 if_ath.c - -rw-r--r-- 1 dan dan 6627 Mar 9 09:23 if_ath_pci.c - -rw-r--r-- 1 dan dan 8421 Feb 13 00:38 if_athioctl.h - -rw-r--r-- 1 dan dan 5274 Oct 27 2008 if_athrate.h - -rw-r--r-- 1 dan dan 28607 Apr 8 12:12 if_athvar.h [dan@laptop:~/tmp/HEAD/src/sys/dev/ath] $ Is this what we're supposed to copy into my 7.2-RELEASE kernel source? - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoJ2IQACgkQCgsXFM/7nTzD+gCeJHHhKhFYhJIy2+4Q71igDNqQ xB8Anj/T1Jv9KDshKG7bJe8B2HAhYx3c =2CDv -----END PGP SIGNATURE----- From dan at langille.org Tue May 12 20:41:12 2009 From: dan at langille.org (Dan Langille) Date: Tue May 12 20:41:18 2009 Subject: EeePC 1000HE + ath on 7.2-RELEASE In-Reply-To: <4A09D884.8050309@langille.org> References: <4A09D884.8050309@langille.org> Message-ID: <4A09DEE1.8080308@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Langille wrote: > I'm trying to get my Atheros Wireless LAN running on my mother's 1000HE. > The NIC runs on current, but we cannot get the USB-serial cable to work > properly. So we are on 7.2-RELEASE now. > > Reading http://wiki.freebsd.org/AsusEee, under 'Atheros Wireless LAN', I > see references to downloading sys/contrib/dev/ath > > I have no such directory in my checkout of HEAD, but I do have this > (note, no contrib directory in the path): > > [dan@laptop:~/tmp/HEAD/src/sys/dev/ath] $ ls -l > total 312 > -rw-r--r-- 1 dan dan 10033 May 7 20:23 ah_osdep.c > -rw-r--r-- 1 dan dan 5152 May 7 20:23 ah_osdep.h > drwxr-xr-x 7 dan dan 512 May 12 10:25 ath_hal > drwxr-xr-x 5 dan dan 512 May 12 10:25 ath_rate > -rw-r--r-- 1 dan dan 214289 May 6 20:35 if_ath.c > -rw-r--r-- 1 dan dan 6627 Mar 9 09:23 if_ath_pci.c > -rw-r--r-- 1 dan dan 8421 Feb 13 00:38 if_athioctl.h > -rw-r--r-- 1 dan dan 5274 Oct 27 2008 if_athrate.h > -rw-r--r-- 1 dan dan 28607 Apr 8 12:12 if_athvar.h > [dan@laptop:~/tmp/HEAD/src/sys/dev/ath] $ > > Is this what we're supposed to copy into my 7.2-RELEASE kernel source? > FWIW, I get: opt_wlan.h no such file or directory from sys/dev/ath/if_ath.c:42 - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoJ3uEACgkQCgsXFM/7nTwrxgCfXvzJ5pKeapGddGJHWUEmMiLc YWYAniowPiqbySR7hpUAF1fSNdUV7DwF =R3EO -----END PGP SIGNATURE----- From guru at unixarea.de Wed May 13 08:20:46 2009 From: guru at unixarea.de (Matthias Apitz) Date: Wed May 13 08:20:52 2009 Subject: laptop Dell M4400 with -CURRENT? In-Reply-To: <20090511122121.GA9961@rebelion.Sisis.de> References: <20090428083627.GA3621@rebelion.Sisis.de> <20090508141755.GB13584@rebelion.Sisis.de> <1241796489.1733.25.camel@balrog.2hip.net> <20090511122121.GA9961@rebelion.Sisis.de> Message-ID: <20090513082036.GA4222@rebelion.Sisis.de> El d?a Monday, May 11, 2009 a las 02:21:21PM +0200, Matthias Apitz escribi?: > El d?a Friday, May 08, 2009 a las 10:28:09AM -0500, Robert Noland escribi?: > > > I have ported the nouveau drm driver. > > > > http://people.freebsd.org/~rnoland/drm-nouveau-043009.patch > > > > It is working on NV50 cards, NV40 was working, but with WITNESS enabled > > I seem to be getting a panic on NV40. My NV40 card seems to be having > > memory issues so I haven't been able to get and/or see the backtrace. I > > think it is just a locking issue which should be pretty easily solved if > > I can get a clear backtrace. > > > > You will need current libdrm and xf86-video-nouveau from ports. > > > > This won't get you 3d right now, but should get you EXA + Xv. > > Hello Robert, > > I have applied your patch and ported xf86-video-nouveau from ports; all > is fine now and the display comes up with 1920x1200 resolution; > > I'm attaching Xorg.0.log so you can see what kind of chips the nouveau > driver is detecting. > > Thanks again for your work and help .... Hello, I have to admit that this message 'all is fine' was to fast; the Xorg came only up *once* and let the KDE3.5.10 fully appear; I was even able to switch the font size from 8 to 12, because with this high resolution it was nearly unreadable. after stopping X with Ctrl-Alt-BS I was never ever able to bring X + KDE up; while KDE is initialising at some point the X goes into 100% of CPU usage; it is not a CPU-loop itself inside the X server, but a loop of SIG 14 as I can proof with truss from another session: SIGNAL 14 (SIGALRM) sigreturn(0xbfbfe500,0xe,0x0,0xbfbfe500,0x0,0x8127070) = 678420552 (0x286fe048) SIGNAL 14 (SIGALRM) sigreturn(0xbfbfe500,0xe,0x0,0xbfbfe500,0x0,0x8127070) = 678420552 (0x286fe048) SIGNAL 14 (SIGALRM) sigreturn(0xbfbfe500,0xe,0x0,0xbfbfe500,0x0,0x8127070) = 678420552 (0x286fe048) SIGNAL 14 (SIGALRM) ... when I only start via ~/.xinitrc a 'xterm' and 'twm' there is no problem, but as soon I'm launching 'startkde' inside such a session the above loop comes up and only power cycle bring the system back to life. What can I do? I have also removed ~/.kde and ~/Desktop to let KDE init a fresh environment, no luck. I'm not using HAL with KDE. The 'vesa' driver works but only gives 1024x??? resolution (don't remember the exact 2nd size right now), but this is not an option to go; is it possible to get higher res with 'vesa'? If someone wants me debugging something, please tell me how; I could even provide SSH access to the laptop (because it is still nearly empty), please contact me off-list for this. Thanks for any hint. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From nate at root.org Wed May 13 23:39:58 2009 From: nate at root.org (Nate Lawson) Date: Wed May 13 23:40:10 2009 Subject: Fighting for the power. In-Reply-To: <20090512182420.K46325@sola.nimnet.asn.au> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> <4A08B10E.4040702@FreeBSD.org> <1242110455.2664.9.camel@slate01> <20090512182420.K46325@sola.nimnet.asn.au> Message-ID: <4A0B43DC.9060708@root.org> Ian Smith wrote: > On Mon, 11 May 2009, Gary Dunn wrote: > > On Tue, 2009-05-12 at 02:13 +0300, Alexander Motin wrote: > > ... > > > > > > What's about general effect, the main idea here is the same as in audio > > > processing: result mostly depends on quality of the worst component. > > > Your system may just have some other consumers which I don't have. For > > > example, desktop CPU instead of mobile, desktop chipset instead of > > > mobile, powerful external video instead of (or even in addition to) > > > built-in, and so on. > > > > > > > Interesting point. Is there a power consumption benchmark for evaluating > > hardware for use with FreeBSD? > > make buildworld, running on battery? :-) > > More seriously: thanks to Nate's earlier niggling, I've been thinking > towards a richer set of power profiles than our {performance,economy} > dichotomy for a while, both in terms of various different work/play and > AC/battery scenarious, and re specific settings that may be more or less > optimal for particular hardware, that could be distributed or advised as > more of a basic working set rather than as a series of 'try this' hints. > FYI, Cyrille Szymanski has implemented a patch to add this kind of power profile support to powerd(8). I'd like to see it finished and committed. -- Nate From smithi at nimnet.asn.au Thu May 14 05:12:06 2009 From: smithi at nimnet.asn.au (Ian Smith) Date: Thu May 14 05:12:19 2009 Subject: Fighting for the power. In-Reply-To: <4A0B43DC.9060708@root.org> References: <49FE1826.4060000@FreeBSD.org> <4A07BC4D.7080604@freebsd.org> <4A081868.6010906@FreeBSD.org> <3a142e750905111308o62a11c8em5465ea9aa1cfaebc@mail.gmail.com> <4A08B10E.4040702@FreeBSD.org> <1242110455.2664.9.camel@slate01> <20090512182420.K46325@sola.nimnet.asn.au> <4A0B43DC.9060708@root.org> Message-ID: <20090514145235.T46325@sola.nimnet.asn.au> On Wed, 13 May 2009, Nate Lawson wrote: > Ian Smith wrote: > > On Mon, 11 May 2009, Gary Dunn wrote: > > > On Tue, 2009-05-12 at 02:13 +0300, Alexander Motin wrote: > > > ... > > > > > > > > What's about general effect, the main idea here is the same as in audio > > > > processing: result mostly depends on quality of the worst component. > > > > Your system may just have some other consumers which I don't have. For > > > > example, desktop CPU instead of mobile, desktop chipset instead of > > > > mobile, powerful external video instead of (or even in addition to) > > > > built-in, and so on. > > > > > > > > > > Interesting point. Is there a power consumption benchmark for evaluating > > > hardware for use with FreeBSD? > > > > make buildworld, running on battery? :-) > > > > More seriously: thanks to Nate's earlier niggling, I've been thinking > > towards a richer set of power profiles than our {performance,economy} > > dichotomy for a while, both in terms of various different work/play and > > AC/battery scenarious, and re specific settings that may be more or less > > optimal for particular hardware, that could be distributed or advised as > > more of a basic working set rather than as a series of 'try this' hints. > > > > FYI, Cyrille Szymanski has implemented a patch to add this kind of power > profile support to powerd(8). I'd like to see it finished and committed. Good to hear, thanks. I'd like to see where it's up to. PR? cheers, Ian [removed current@ cc as I'm not subscribed - add it back if relevant] From guru at unixarea.de Thu May 14 08:46:22 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu May 14 08:46:35 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? Message-ID: <20090514084617.GA3459@rebelion.Sisis.de> Hello, I've a brand new Dell M4400 laptop running CURRENT; the nVidia Corporation Quadro FX 770M ship is currently not fully supported by the nouveau driver and I'm bound to 'vesa' driver for that, at least for the moment. The resolution of the laptop is normally 1920x1200, but 'vesa' seems not been willing to use this res. even if the Xorg.0.log has lines saying that there is an internal mode like that but not being used: *Mode: 17d (1920x1200) ModeAttributes: 0x3bf WinAAttributes: 0x7 ... (II) VESA(0): Monitor0: Using default hsync range of 31.50-37.90 kHz (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz (II) VESA(0): Not using built-in mode "1920x1200" (no mode of this name) ... (II) VESA(0): Not using built-in mode "1920x1200" (hsync out of range) (--) VESA(0): Virtual size is 1280x720 (pitch 1280) (**) VESA(0): *Built-in mode "1280x720" (**) VESA(0): *Built-in mode "800x600" (**) VESA(0): *Built-in mode "640x480" and at the end it gives 1280x720 (which is not bad but fare away from 1920x1200). My Display section in xorg.conf has: SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1200" "1280x720" EndSubSection Any idea how I could get 1920x1200 with the 'vesa' driver in Xorg 1.6? I need that box urgently for my daily work... Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From guru at unixarea.de Thu May 14 09:57:05 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu May 14 09:57:17 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <200905141145.15357.pieter@degoeje.nl> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141145.15357.pieter@degoeje.nl> Message-ID: <20090514095700.GA5105@rebelion.Sisis.de> El d?a Thursday, May 14, 2009 a las 11:45:15AM +0200, Pieter de Goeje escribi?: > On Thursday 14 May 2009 10:46:17 Matthias Apitz wrote: > > I've a brand new Dell M4400 laptop running CURRENT; the nVidia > > Corporation Quadro FX 770M > > ship is currently not fully supported by the nouveau driver and I'm > > bound to 'vesa' driver for that, at least for the moment. The resolution > > of the laptop is normally 1920x1200, but 'vesa' seems not been willing to > > use this res. even if the Xorg.0.log has lines saying that there is an > > internal mode like that but not being used: > > > Have you considered using the 'nv' driver? I think it supports your graphics card. Yes; but this gives: $ X -retro X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-CURRENT i386 Current Operating System: FreeBSD current 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Mo n May 11 13:31:04 UTC 2009 guru@current:/usr/obj/usr/src/sys/REBELION-CURREN T i386 Build Date: 28 April 2009 11:44:04AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 11:51:19 2009 (==) Using config file: "/etc/X11/xorg.conf" (EE) No devices detected. Fatal server error: no screens found and /var/log/Xorg.0.log has: ... (--) PCI:*(0@1:0:0) nVidia Corporation Quadro FX 770M rev 161, Mem @ 0xf5000000/16777216, 0xe0000000/268435456, 0xf2000000/33554432, I/O @ 0x0000df00/128, BIOS @ 0x????????/65536 ... (II) Primary Device is: PCI 01@00:00:0 (WW) NV: Ignoring unsupported device 0x10de065c (Quadro FX 770M) at 01@00:00:0 (EE) No devices detected. maybe I could fake the id 0x10de065c to something known my the 'nv' driver? any idea? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From pieter at degoeje.nl Thu May 14 09:57:24 2009 From: pieter at degoeje.nl (Pieter de Goeje) Date: Thu May 14 09:57:30 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <20090514084617.GA3459@rebelion.Sisis.de> References: <20090514084617.GA3459@rebelion.Sisis.de> Message-ID: <200905141145.15357.pieter@degoeje.nl> On Thursday 14 May 2009 10:46:17 Matthias Apitz wrote: > I've a brand new Dell M4400 laptop running CURRENT; the nVidia > Corporation Quadro FX 770M > ship is currently not fully supported by the nouveau driver and I'm > bound to 'vesa' driver for that, at least for the moment. The resolution > of the laptop is normally 1920x1200, but 'vesa' seems not been willing to > use this res. even if the Xorg.0.log has lines saying that there is an > internal mode like that but not being used: > Have you considered using the 'nv' driver? I think it supports your graphics card. -- Pieter de Goeje From pieter at degoeje.nl Thu May 14 10:34:08 2009 From: pieter at degoeje.nl (Pieter de Goeje) Date: Thu May 14 10:34:21 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <20090514095700.GA5105@rebelion.Sisis.de> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141145.15357.pieter@degoeje.nl> <20090514095700.GA5105@rebelion.Sisis.de> Message-ID: <200905141234.05410.pieter@degoeje.nl> On Thursday 14 May 2009 11:57:00 Matthias Apitz wrote: > El d?a Thursday, May 14, 2009 a las 11:45:15AM +0200, Pieter de Goeje escribi?: > > > On Thursday 14 May 2009 10:46:17 Matthias Apitz wrote: > > > I've a brand new Dell M4400 laptop running CURRENT; the nVidia > > > Corporation Quadro FX 770M > > > ship is currently not fully supported by the nouveau driver and I'm > > > bound to 'vesa' driver for that, at least for the moment. The resolution > > > of the laptop is normally 1920x1200, but 'vesa' seems not been willing to > > > use this res. even if the Xorg.0.log has lines saying that there is an > > > internal mode like that but not being used: > > > > > Have you considered using the 'nv' driver? I think it supports your graphics card. > > Yes; but this gives: > > $ X -retro > > X.Org X Server 1.6.0 > Release Date: 2009-2-25 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 8.0-CURRENT i386 > Current Operating System: FreeBSD current 8.0-CURRENT FreeBSD > 8.0-CURRENT #1: Mo > n May 11 13:31:04 UTC 2009 > guru@current:/usr/obj/usr/src/sys/REBELION-CURREN > T i386 > Build Date: 28 April 2009 11:44:04AM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 11:51:19 2009 > (==) Using config file: "/etc/X11/xorg.conf" > (EE) No devices detected. > > Fatal server error: > no screens found > > and /var/log/Xorg.0.log has: > > ... > (--) PCI:*(0@1:0:0) nVidia Corporation Quadro FX 770M rev 161, Mem @ 0xf5000000/16777216, > 0xe0000000/268435456, 0xf2000000/33554432, I/O @ 0x0000df00/128, BIOS @ 0x????????/65536 > ... > (II) Primary Device is: PCI 01@00:00:0 > (WW) NV: Ignoring unsupported device 0x10de065c (Quadro FX 770M) at 01@00:00:0 > (EE) No devices detected. > > maybe I could fake the id 0x10de065c to something known my the 'nv' > driver? any idea? > > matthias > You could try that, but I see that you're running 32bit FreeBSD, which should enable you to use te nvidia binary driver (x11/nvidia-driver). I know it works excellent on my laptop (i386, 7-STABLE w/ GeForce 8400M). -- Pieter de Goeje From guru at unixarea.de Thu May 14 11:19:58 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu May 14 11:20:10 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <200905141234.05410.pieter@degoeje.nl> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141145.15357.pieter@degoeje.nl> <20090514095700.GA5105@rebelion.Sisis.de> <200905141234.05410.pieter@degoeje.nl> Message-ID: <20090514111954.GA7288@rebelion.Sisis.de> El d?a Thursday, May 14, 2009 a las 12:34:04PM +0200, Pieter de Goeje escribi?: > You could try that, but I see that you're running 32bit FreeBSD, which should enable > you to use te nvidia binary driver (x11/nvidia-driver). > I know it works excellent on my laptop (i386, 7-STABLE w/ GeForce 8400M). Thanks for your hint; I've installed this port x11/nvidia-driver and did what the port requested at the end about /boot/loader.conf and /etc/rc.conf; I run # X -configure and got a fresh xorg.conf created which as well contains 'nvidia' as the driver: Section "Device" Identifier "Card0" Driver "nvidia" VendorName "nVidia Corporation" BoardName "Quadro FX 770M" BusID "PCI:1:0:0" EndSection but when I run: # X -retro -config /root/xorg.conf.new X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.0-CURRENT i386 Current Operating System: FreeBSD current 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Mon May 11 13:31:04 UTC 2009 guru@current:/usr/obj/usr/src/sys/REBELION-CURRENT i386 Build Date: 28 April 2009 11:44:04AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 13:05:56 2009 (++) Using config file: "/root/xorg.conf.new" NVIDIA: failed to set MTRR 0xe0000000, 0M (write-combining) NVIDIA: failed to set MTRR 0xe0000000, 0M (write-combining) it just hard-locks the system :-( any idea? could you send me off-list your xorg.conf to check it? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From pieter at degoeje.nl Thu May 14 11:54:30 2009 From: pieter at degoeje.nl (Pieter de Goeje) Date: Thu May 14 11:54:43 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <20090514111954.GA7288@rebelion.Sisis.de> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141234.05410.pieter@degoeje.nl> <20090514111954.GA7288@rebelion.Sisis.de> Message-ID: <200905141354.27207.pieter@degoeje.nl> On Thursday 14 May 2009 13:19:54 Matthias Apitz wrote: > El d?a Thursday, May 14, 2009 a las 12:34:04PM +0200, Pieter de Goeje escribi?: > > > You could try that, but I see that you're running 32bit FreeBSD, which should enable > > you to use te nvidia binary driver (x11/nvidia-driver). > > I know it works excellent on my laptop (i386, 7-STABLE w/ GeForce 8400M). > > Thanks for your hint; I've installed this port x11/nvidia-driver and did > what the port requested at the end about /boot/loader.conf and > /etc/rc.conf; > > I run > > # X -configure > > and got a fresh xorg.conf created which as well contains 'nvidia' as the > driver: > > Section "Device" > Identifier "Card0" > Driver "nvidia" > VendorName "nVidia Corporation" > BoardName "Quadro FX 770M" > BusID "PCI:1:0:0" > EndSection > > but when I run: > > # X -retro -config /root/xorg.conf.new > > X.Org X Server 1.6.0 > Release Date: 2009-2-25 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 8.0-CURRENT i386 > Current Operating System: FreeBSD current 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Mon May 11 13:31:04 UTC 2009 > guru@current:/usr/obj/usr/src/sys/REBELION-CURRENT i386 > Build Date: 28 April 2009 11:44:04AM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 13:05:56 2009 > (++) Using config file: "/root/xorg.conf.new" > NVIDIA: failed to set MTRR 0xe0000000, 0M (write-combining) > NVIDIA: failed to set MTRR 0xe0000000, 0M (write-combining) > > it just hard-locks the system :-( > > any idea? could you send me off-list your xorg.conf to check it? > > matthias I don't know if you can install/"downgrade" to 7-STABLE, but perhaps the nvidia driver is broken on -CURRENT. Or you might try posting this problem on the nvnews.net fora. My xorg.conf is just like yours, so I don't think sending mine will help. Sorry, I'm all out of ideas here :-/ -- Pieter de Goeje From guru at unixarea.de Thu May 14 11:57:53 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu May 14 11:58:05 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <200905141234.05410.pieter@degoeje.nl> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141145.15357.pieter@degoeje.nl> <20090514095700.GA5105@rebelion.Sisis.de> <200905141234.05410.pieter@degoeje.nl> Message-ID: <20090514115735.GA8424@rebelion.Sisis.de> El d?a Thursday, May 14, 2009 a las 12:34:04PM +0200, Pieter de Goeje escribi?: > > > > maybe I could fake the id 0x10de065c to something known my the 'nv' > > driver? any idea? > > > > matthias > > > You could try that, ... I've tried to fake the ChipID with: Section "Device" Identifier "Card0" ChipID 0x033f # fake a Quadro FX 700 Driver "nv" # VendorName "nVidia Corporation" # BoardName "Quadro FX 770M" # BusID "PCI:1:0:0" EndSection but the value of ChipID it is not used by 'nv': (II) Primary Device is: PCI 01@00:00:0 (WW) NV: Ignoring unsupported device 0x10de065c (Quadro FX 770M) at 01@00:00:0 (EE) No devices detected. now I'm really clueless :-( matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From shoesoft at gmx.net Thu May 14 15:18:19 2009 From: shoesoft at gmx.net (Stefan Ehmann) Date: Thu May 14 15:18:25 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <20090514084617.GA3459@rebelion.Sisis.de> References: <20090514084617.GA3459@rebelion.Sisis.de> Message-ID: <200905141651.35948.shoesoft@gmx.net> On Thursday 14 May 2009 10:46:17 Matthias Apitz wrote: > Hello, > > I've a brand new Dell M4400 laptop running CURRENT; the nVidia > Corporation Quadro FX 770M > ship is currently not fully supported by the nouveau driver and I'm > bound to 'vesa' driver for that, at least for the moment. The resolution > of the laptop is normally 1920x1200, but 'vesa' seems not been willing to > use this res. even if the Xorg.0.log has lines saying that there is an > internal mode like that but not being used: ... > (II) VESA(0): Monitor0: Using default hsync range of 31.50-37.90 kHz > (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz > > (II) VESA(0): Not using built-in mode "1920x1200" (no mode of this name) > ... > (II) VESA(0): Not using built-in mode "1920x1200" (hsync out of range) Adding a custom modeline and/or adjusting the hsync/vrefresh values should fix this. I'd guess the fallback to the default hsync/vrefresh values is the problem. Booting a linux live CD might provide some usable values. From pete at altadena.net Thu May 14 16:00:16 2009 From: pete at altadena.net (Pete Carah) Date: Thu May 14 16:00:22 2009 Subject: AR9280 Message-ID: <4A0C3A73.1030304@altadena.net> I have a new laptop that came with a Ralink N card that wasn't supported in either Fedora or FreeBSD; I substituted an Atheros card (boy, these things are getting cheap nowadays - ABGN for $53) (the antennas don't appear to handle A very well, not like my old sony, but they do handle it). It works fine in Fedora 10 and I got it partly because grepping the source for 9280 showed what appeared to be support in FBSD. However (7.2-stable sup'd yesterday) there are a few files still missing. Is there a way to get the rest of this driver? (like in HEAD, maybe, if it is compatible enough?) Sam - I can do some debugging but don't have time for a lot, so if things are "almost" finished it is probably OK. (I do linux device drivers at work so can handle generic kernel debugging, though I'm not too familiar with fbsd locking in its current incarnation (linux is missing some things like recursive locks that I'd want, and is starting to use rcu for read/write locking; I don't know about fbsd...) Both of the networks I normally access are WPA2; one PSK and the other PEAP. The linux driver handles the PEAP and I haven't tried it with the PSK network yet. Can't try vista due to a grub malfunction :-( (it handles bsd fine, and of course fedora also but just reboots when you try vista. It's nice to have a laptop with enough disk to triple-boot.) -- Pete From sam at freebsd.org Thu May 14 16:46:52 2009 From: sam at freebsd.org (Sam Leffler) Date: Thu May 14 16:46:58 2009 Subject: AR9280 In-Reply-To: <4A0C3A73.1030304@altadena.net> References: <4A0C3A73.1030304@altadena.net> Message-ID: <4A0C42E1.2080407@freebsd.org> Pete Carah wrote: > I have a new laptop that came with a Ralink N card that wasn't supported > in either Fedora or FreeBSD; I substituted an Atheros card (boy, these > things are getting cheap nowadays - ABGN for $53) (the antennas don't > appear to handle A very well, not like my old sony, but they do handle > it). It works fine in Fedora 10 and I got it partly because grepping > the source for 9280 showed what appeared to be support in FBSD. However > (7.2-stable sup'd yesterday) there are a few files still missing. Is > there a way to get the rest of this driver? (like in HEAD, maybe, if it > is compatible enough?) > > Sam - I can do some debugging but don't have time for a lot, so if > things are "almost" finished it is probably OK. (I do linux device > drivers at work so can handle generic kernel debugging, though I'm not > too familiar with fbsd locking in its current incarnation (linux is > missing some things like recursive locks that I'd want, and is starting > to use rcu for read/write locking; I don't know about fbsd...) > > Both of the networks I normally access are WPA2; one PSK and the other > PEAP. The linux driver handles the PEAP and I haven't tried it with the > PSK network yet. Can't try vista due to a grub malfunction :-( (it > handles bsd fine, and of course fedora also but just reboots when you > try vista. It's nice to have a laptop with enough disk to triple-boot.) > Code is in head and needs backporting. I have no time. Everything you need should be in the sys/dev/ath/ath_hal/ar5416 directory. It might be possible to just apply the commit from HEAD though there's been significant divergence so possibly not. Remember it does only legacy mode (no 11n) and seems to have some bugs (chip locks up and gets reset). Atheros only cares about linux so fixes must come from sifting linux crud. Sam From freebsd at blacquiere.nl Fri May 15 09:13:09 2009 From: freebsd at blacquiere.nl (Robert Blacquiere) Date: Fri May 15 09:13:17 2009 Subject: Xorg on X300 lenovo with 7.2-RELEASE Message-ID: <20090515085300.GD30349@macmini.blacquiere.nl> Hi all, I installed a fresh version of FreeBSD 7.2 on my lenovo X300. It was running OpenBSD for some time. For some reason I can't get Xorg to display any thing on screen except backlight. In the Xorg.0.log seems no real issues. I have run freebsd 7.0R with Xorg before without any problems. I tried also 8.0-CURRENT but it had the same problems so I tried the 7.2R. They all produce the same backlighted black screen. What can I do to get things running, any hints? Regards Logs and xorg.conf. Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/local/lib/xorg/modules" FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" EndSection Section "Module" Load "dbe" Load "dri" Load "dri2" Load "extmod" Load "glx" Load "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "SWcursor" # [] #Option "ColorKey" # #Option "CacheLines" # #Option "Dac6Bit" # [] #Option "DRI" # [] #Option "NoDDC" # [] #Option "ShowCache" # [] #Option "XvMCSurfaces" # #Option "PageFlip" # [] Identifier "Card0" Driver "intel" VendorName "Intel Corporation" BoardName "Mobile GM965/GL960 Integrated Graphics Controller" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection X.Org X Server 1.6.0 Release Date: 2009-2-25 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.2-RELEASE amd64 Current Operating System: FreeBSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 21 April 2009 12:25:49AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 15 10:41:24 2009 (++) Using config file: "./xorg.conf.new" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Automatically adding devices (==) Automatically enabling devices (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, built-ins (**) ModulePath set to "/usr/local/lib/xorg/modules" (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 (II) Loader magic: 0x3d20 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on freebsd (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xfa000000/1048576, 0xe0000000/268435456, I/O @ 0x00001800/8, BIOS @ 0x????????/65536 (--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xfa100000/1048576 (II) System resource ranges: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded. This was enabled by default and also specified in the config file. (II) "dri" will be loaded. This was enabled by default and also specified in the config file. (II) "dri2" will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: "dri2" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri2.so (II) Module dri2: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DRI2 (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so (II) Module record: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension RECORD (II) LoadModule: "intel" (II) Loading /usr/local/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.6.3 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, Mobile Intel® GM45 Express Chipset, Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41 (II) Primary Device is: PCI 00@00:02:0 (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) resource ranges after probing: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/local/lib/xorg/modules//libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.6.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 5.0 (==) intel(0): Depth 24, (--) framebuffer bpp 32 (==) intel(0): RGB weight 888 (==) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM (--) intel(0): Chipset: "965GM" (--) intel(0): Linear framebuffer at 0xE0000000 (--) intel(0): IO registers at addr 0xFA000000 (==) intel(0): Using EXA for acceleration (II) intel(0): 2 display pipes available. (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Module "i2c" already built-in (II) intel(0): Output VGA using monitor section Monitor0 (II) intel(0): Output LVDS has no monitor section (II) intel(0): I2C bus "LVDSDDC_C" initialized. (II) intel(0): Attempting to determine panel fixed mode. (II) intel(0): I2C device "LVDSDDC_C:E-EDID segment register" registered at address 0x60. (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): EDID vendor "LEN", prod id 16500 (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72. (II) intel(0): No SDVO device found on SDVOC (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear (II) intel(0): Resizable framebuffer: not available (1 3) (II) intel(0): EDID vendor "LEN", prod id 16500 (II) intel(0): Output VGA disconnected (II) intel(0): Output LVDS connected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output LVDS using initial mode 1440x900 (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear (II) intel(0): detected 512 kB GTT. (II) intel(0): detected 7676 kB stolen memory. (==) intel(0): video overlay key set to 0x101fe (==) intel(0): Will not try to enable page flipping (==) intel(0): Triple buffering disabled (==) intel(0): Using gamma correction (1.0, 1.0, 1.0) (==) intel(0): DPI set to (96, 96) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.6.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.4 (II) Loading sub module "exa" (II) LoadModule: "exa" (II) Loading /usr/local/lib/xorg/modules//libexa.so (II) Module exa: vendor="X.Org Foundation" compiled for 1.6.0, module version = 2.4.0 ABI class: X.Org Video Driver, version 5.0 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Module "ramdac" already built-in (II) intel(0): Comparing regs from server start up to After PreInit (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a (WW) intel(0): PP_STATUS before: on, ready, sequencing idle (WW) intel(0): PP_STATUS after: on, ready, sequencing on (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (II) intel(0): Kernel reported 491520 total, 0 used (II) intel(0): I830CheckAvailableMemory: 1966080 kB available (WW) intel(0): DRI2 requires UXA drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: Searching for BusID pci:0000:00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 (II) [drm] DRM interface version 1.2 (II) [drm] DRM open master succeeded. (II) intel(0): [drm] Using the DRM lock SAREA also for drawables. (II) intel(0): [drm] framebuffer mapped by ddx driver (II) intel(0): [drm] added 1 reserved context for kernel (II) intel(0): X context handle = 0x2 (II) intel(0): [drm] installed DRM signal handler (**) intel(0): Framebuffer compression disabled (**) intel(0): Tiling enabled (==) intel(0): VideoRam: 262144 KB (II) intel(0): Attempting memory allocation with tiled buffers. (II) intel(0): Tiled allocation successful. (II) intel(0): [drm] Registers = 0xfa000000 (II) intel(0): [drm] ring buffer = 0xe0000000 (II) intel(0): [drm] mapped front buffer at 0xe012b000, handle = 0xe012b000 (II) intel(0): [drm] mapped back buffer at 0xe22ec000, handle = 0xe22ec000 (II) intel(0): [drm] mapped depth buffer at 0xe2b5c000, handle = 0xe2b5c000 (II) intel(0): [drm] mapped classic textures at 0xe33cc000, handle = 0xe33cc000 (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432 (II) intel(0): [dri] visual configs initialized (II) intel(0): Page Flipping disabled (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear (II) EXA(0): Offscreen pixmap area of 26542080 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) Composite (RENDER acceleration) (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): [DRI] installation complete (II) intel(0): xf86BindGARTMemory: bind key 27 at 0x0077f000 (pgoffset 1919) (II) intel(0): xf86BindGARTMemory: bind key 28 at 0x0099b000 (pgoffset 2459) (II) intel(0): xf86BindGARTMemory: bind key 29 at 0x022eb000 (pgoffset 8939) (II) intel(0): xf86BindGARTMemory: bind key 30 at 0x022ec000 (pgoffset 8940) (II) intel(0): xf86BindGARTMemory: bind key 31 at 0x02b5c000 (pgoffset 11100) (II) intel(0): xf86BindGARTMemory: bind key 32 at 0x033cc000 (pgoffset 13260) (II) intel(0): Fixed memory allocation layout: (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB) (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB) (II) intel(0): 0x0002a000-0x00129fff: fake bufmgr (1024 kB) (II) intel(0): 0x0012a000-0x0012afff: overlay registers (4 kB) (II) intel(0): 0x0012b000-0x0099afff: front buffer (8640 kB) (II) intel(0): 0x0077f000: end of stolen memory (II) intel(0): 0x0099b000-0x022eafff: exa offscreen (25920 kB) (II) intel(0): 0x022eb000-0x022ebfff: power context (4 kB) (II) intel(0): 0x022ec000-0x02b5bfff: back buffer (8640 kB) (II) intel(0): 0x02b5c000-0x033cbfff: depth buffer (8640 kB) (II) intel(0): 0x033cc000-0x053cbfff: classic textures (32768 kB) (II) intel(0): 0x10000000: end of aperture (II) intel(0): using SSC reference clock of 100 MHz (II) intel(0): Selecting standard 18 bit TMDS pixel format. (II) intel(0): Output configuration: (II) intel(0): Pipe A is off (II) intel(0): Display plane A is now disabled and connected to pipe A. (II) intel(0): Pipe B is on (II) intel(0): Display plane B is now enabled and connected to pipe B. (II) intel(0): Output VGA is connected to pipe none (II) intel(0): Output LVDS is connected to pipe B (II) intel(0): [drm] dma control initialized, using IRQ 16 (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. (II) intel(0): DPMS enabled (==) intel(0): Intel XvMC decoder disabled (II) intel(0): Set up textured video (II) intel(0): Set up overlay video (II) intel(0): direct rendering: XF86DRI Enabled (--) RandR disabled (II) Initializing built-in extension Generic Event Extension (II) Initializing built-in extension SHAPE (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension BIG-REQUESTS (II) Initializing built-in extension SYNC (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-MISC (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 (II) intel(0): Setting screen physical size to 287 x 180 (EE) config/hal: couldn't initialise context: (null) ((null)) (II) intel(0): xf86UnbindGARTMemory: unbind key 27 (II) intel(0): xf86UnbindGARTMemory: unbind key 28 (II) intel(0): xf86UnbindGARTMemory: unbind key 29 (II) intel(0): xf86UnbindGARTMemory: unbind key 30 (II) intel(0): xf86UnbindGARTMemory: unbind key 31 (II) intel(0): xf86UnbindGARTMemory: unbind key 32 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xfffffffe806d4000 at 0x8006b4000 (II) intel(0): [drm] Closed DRM master. From guru at unixarea.de Fri May 15 12:52:58 2009 From: guru at unixarea.de (Matthias Apitz) Date: Fri May 15 12:53:11 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <200905141651.35948.shoesoft@gmx.net> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141651.35948.shoesoft@gmx.net> Message-ID: <20090515125250.GA11380@rebelion.Sisis.de> El d?a Thursday, May 14, 2009 a las 04:51:34PM +0200, Stefan Ehmann escribi?: > On Thursday 14 May 2009 10:46:17 Matthias Apitz wrote: > > Hello, > > > > I've a brand new Dell M4400 laptop running CURRENT; the nVidia > > Corporation Quadro FX 770M > > ship is currently not fully supported by the nouveau driver and I'm > > bound to 'vesa' driver for that, at least for the moment. The resolution > > of the laptop is normally 1920x1200, but 'vesa' seems not been willing to > > use this res. even if the Xorg.0.log has lines saying that there is an > > internal mode like that but not being used: > ... > > (II) VESA(0): Monitor0: Using default hsync range of 31.50-37.90 kHz > > (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz > > > > (II) VESA(0): Not using built-in mode "1920x1200" (no mode of this name) > > ... > > (II) VESA(0): Not using built-in mode "1920x1200" (hsync out of range) > > Adding a custom modeline and/or adjusting the hsync/vrefresh values should fix > this. I'd guess the fallback to the default hsync/vrefresh values is the > problem. > > Booting a linux live CD might provide some usable values. Yes, this worked; but it was terrible slow on window movements; I've got a small fix for the driver x11-drivers/xf86-video-nv and the card is now working as it should with the 'nv' module. Thanks in any case matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From martinsm at gn.apc.org Fri May 15 13:44:39 2009 From: martinsm at gn.apc.org (Martin Smith) Date: Fri May 15 13:44:45 2009 Subject: wpa supplicant fails to start Message-ID: <49281.80.177.154.53.1242394038.squirrel@sqmail.gn.apc.org> >From dmesg: May 15 13:38:32 lp2 kernel: ath0: mem 0x88000000-0x8800ffff irq 11 at device 0.0 on cardbus0 May 15 13:38:32 lp2 kernel: ath0: [ITHREAD] May 15 13:38:32 lp2 kernel: ath0: AR2417 mac 15.0 RF5424 phy 7.0 My wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="myssid" scan_ssid=1 key_mgmt=WPA-PSK psk="my wpa secret" } I have put this together using both the handbook and the wpa_supplicant.conf man page, do I need to add anything else? I get this error: lp2# wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf ioctl[SIOCG80211, op 98, len 32]: Invalid argument Failed to initialize driver interface ELOOP: remaining socket: sock=4 eloop_data=0x28406140 user_data=0x2840d040 handler=0x8069f50 I obviously have something wrong, can anyone point me in the right direction. System is current as of yesterday rebuilt. Card is TP-Link TL-WN310G Machine is a Thinkpad X23 lp2# ifconfig -a fxp0: flags=8843 metric 0 mtu 1500 options=2009 ether 00:d0:59:b5:a2:0c inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 ath0: flags=8802 metric 0 mtu 2290 ether 00:23:cd:c5:c3:c9 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier Thanks for any pointers -- Martin From rnoland at FreeBSD.org Fri May 15 14:25:01 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Fri May 15 14:25:12 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <20090515125250.GA11380@rebelion.Sisis.de> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141651.35948.shoesoft@gmx.net> <20090515125250.GA11380@rebelion.Sisis.de> Message-ID: <1242397462.1755.89.camel@balrog.2hip.net> On Fri, 2009-05-15 at 14:52 +0200, Matthias Apitz wrote: > El d?a Thursday, May 14, 2009 a las 04:51:34PM +0200, Stefan Ehmann escribi?: > > > On Thursday 14 May 2009 10:46:17 Matthias Apitz wrote: > > > Hello, > > > > > > I've a brand new Dell M4400 laptop running CURRENT; the nVidia > > > Corporation Quadro FX 770M > > > ship is currently not fully supported by the nouveau driver and I'm > > > bound to 'vesa' driver for that, at least for the moment. The resolution > > > of the laptop is normally 1920x1200, but 'vesa' seems not been willing to > > > use this res. even if the Xorg.0.log has lines saying that there is an > > > internal mode like that but not being used: > > ... > > > (II) VESA(0): Monitor0: Using default hsync range of 31.50-37.90 kHz > > > (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz > > > > > > (II) VESA(0): Not using built-in mode "1920x1200" (no mode of this name) > > > ... > > > (II) VESA(0): Not using built-in mode "1920x1200" (hsync out of range) > > > > Adding a custom modeline and/or adjusting the hsync/vrefresh values should fix > > this. I'd guess the fallback to the default hsync/vrefresh values is the > > problem. > > > > Booting a linux live CD might provide some usable values. > > Yes, this worked; but it was terrible slow on window movements; > I've got a small fix for the driver x11-drivers/xf86-video-nv and the > card is now working as it should with the 'nv' module. What patch? If it needs review and committing upstream, please send it to me... robert. > Thanks in any case > > matthias -- Robert Noland FreeBSD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090515/1fb0154a/attachment.pgp From rnoland at FreeBSD.org Fri May 15 14:36:00 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Fri May 15 14:36:07 2009 Subject: Xorg on X300 lenovo with 7.2-RELEASE In-Reply-To: <20090515085300.GD30349@macmini.blacquiere.nl> References: <20090515085300.GD30349@macmini.blacquiere.nl> Message-ID: <1242396305.1755.84.camel@balrog.2hip.net> On Fri, 2009-05-15 at 10:53 +0200, Robert Blacquiere wrote: > Hi all, > > I installed a fresh version of FreeBSD 7.2 on my lenovo X300. It was > running OpenBSD for some time. For some reason I can't get Xorg to > display any thing on screen except backlight. In the Xorg.0.log seems no > real issues. I have run freebsd 7.0R with Xorg before without any > problems. I tried also 8.0-CURRENT but it had the same problems so I > tried the 7.2R. They all produce the same backlighted black screen. > > What can I do to get things running, any hints? add: dbus_enable="YES" hald_enable="YES" to /etc/rc.conf robert. > Regards > > Logs and xorg.conf. > > > Section "ServerLayout" > Identifier "X.org Configured" > Screen 0 "Screen0" 0 0 > InputDevice "Mouse0" "CorePointer" > InputDevice "Keyboard0" "CoreKeyboard" > EndSection > > Section "Files" > ModulePath "/usr/local/lib/xorg/modules" > FontPath "/usr/local/lib/X11/fonts/misc/" > FontPath "/usr/local/lib/X11/fonts/TTF/" > FontPath "/usr/local/lib/X11/fonts/OTF" > FontPath "/usr/local/lib/X11/fonts/Type1/" > FontPath "/usr/local/lib/X11/fonts/100dpi/" > FontPath "/usr/local/lib/X11/fonts/75dpi/" > EndSection > > Section "Module" > Load "dbe" > Load "dri" > Load "dri2" > Load "extmod" > Load "glx" > Load "record" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > Section "Monitor" > Identifier "Monitor0" > VendorName "Monitor Vendor" > ModelName "Monitor Model" > EndSection > > Section "Device" > ### Available Driver options are:- > ### Values: : integer, : float, : "True"/"False", > ### : "String", : " Hz/kHz/MHz" > ### [arg]: arg optional > #Option "NoAccel" # [] > #Option "SWcursor" # [] > #Option "ColorKey" # > #Option "CacheLines" # > #Option "Dac6Bit" # [] > #Option "DRI" # [] > #Option "NoDDC" # [] > #Option "ShowCache" # [] > #Option "XvMCSurfaces" # > #Option "PageFlip" # [] > Identifier "Card0" > Driver "intel" > VendorName "Intel Corporation" > BoardName "Mobile GM965/GL960 Integrated Graphics Controller" > BusID "PCI:0:2:0" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor "Monitor0" > SubSection "Display" > Viewport 0 0 > Depth 1 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 4 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 8 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 15 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 16 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 24 > EndSubSection > EndSection > > > > X.Org X Server 1.6.0 > Release Date: 2009-2-25 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.2-RELEASE amd64 > Current Operating System: FreeBSD 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 07:18:07 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > Build Date: 21 April 2009 12:25:49AM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 15 10:41:24 2009 > (++) Using config file: "./xorg.conf.new" > (==) ServerLayout "X.org Configured" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "Monitor0" > (**) | |-->Device "Card0" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (==) Automatically adding devices > (==) Automatically enabling devices > (**) FontPath set to: > /usr/local/lib/X11/fonts/misc/, > /usr/local/lib/X11/fonts/TTF/, > /usr/local/lib/X11/fonts/OTF, > /usr/local/lib/X11/fonts/Type1/, > /usr/local/lib/X11/fonts/100dpi/, > /usr/local/lib/X11/fonts/75dpi/, > /usr/local/lib/X11/fonts/misc/, > /usr/local/lib/X11/fonts/TTF/, > /usr/local/lib/X11/fonts/OTF, > /usr/local/lib/X11/fonts/Type1/, > /usr/local/lib/X11/fonts/100dpi/, > /usr/local/lib/X11/fonts/75dpi/, > built-ins > (**) ModulePath set to "/usr/local/lib/xorg/modules" > (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. > (WW) Disabling Mouse0 > (WW) Disabling Keyboard0 > (II) Loader magic: 0x3d20 > (II) Module ABI versions: > X.Org ANSI C Emulation: 0.4 > X.Org Video Driver: 5.0 > X.Org XInput driver : 4.0 > X.Org Server Extension : 2.0 > (II) Loader running on freebsd > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > (--) PCI:*(0@0:2:0) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xfa000000/1048576, 0xe0000000/268435456, I/O @ 0x00001800/8, BIOS @ 0x????????/65536 > (--) PCI: (0@0:2:1) Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller rev 12, Mem @ 0xfa100000/1048576 > (II) System resource ranges: > [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. > (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. > (II) "glx" will be loaded. This was enabled by default and also specified in the config file. > (II) "record" will be loaded. This was enabled by default and also specified in the config file. > (II) "dri" will be loaded. This was enabled by default and also specified in the config file. > (II) "dri2" will be loaded. This was enabled by default and also specified in the config file. > (II) LoadModule: "dbe" > (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so > (II) Module dbe: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.0.0 > Module class: X.Org Server Extension > ABI class: X.Org Server Extension, version 2.0 > (II) Loading extension DOUBLE-BUFFER > (II) LoadModule: "dri" > (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so > (II) Module dri: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.0.0 > ABI class: X.Org Server Extension, version 2.0 > (II) Loading extension XFree86-DRI > (II) LoadModule: "dri2" > (II) Loading /usr/local/lib/xorg/modules/extensions//libdri2.so > (II) Module dri2: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.0.0 > ABI class: X.Org Server Extension, version 2.0 > (II) Loading extension DRI2 > (II) LoadModule: "extmod" > (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so > (II) Module extmod: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.0.0 > Module class: X.Org Server Extension > ABI class: X.Org Server Extension, version 2.0 > (II) Loading extension MIT-SCREEN-SAVER > (II) Loading extension XFree86-VidModeExtension > (II) Loading extension XFree86-DGA > (II) Loading extension DPMS > (II) Loading extension XVideo > (II) Loading extension XVideo-MotionCompensation > (II) Loading extension X-Resource > (II) LoadModule: "glx" > (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so > (II) Module glx: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.0.0 > ABI class: X.Org Server Extension, version 2.0 > (==) AIGLX disabled > (II) Loading extension GLX > (II) LoadModule: "record" > (II) Loading /usr/local/lib/xorg/modules/extensions//librecord.so > (II) Module record: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.13.0 > Module class: X.Org Server Extension > ABI class: X.Org Server Extension, version 2.0 > (II) Loading extension RECORD > (II) LoadModule: "intel" > (II) Loading /usr/local/lib/xorg/modules/drivers//intel_drv.so > (II) Module intel: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 2.6.3 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 5.0 > (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, > i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, > E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ, > 965GM, 965GME/GLE, G33, Q35, Q33, > Mobile Intel? GM45 Express Chipset, > Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41 > (II) Primary Device is: PCI 00@00:02:0 > (II) resource ranges after xf86ClaimFixedResources() call: > [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [3] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [4] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > (II) resource ranges after probing: > [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] > [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] > [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] > [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] > [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] > (II) Loading sub module "vgahw" > (II) LoadModule: "vgahw" > (II) Loading /usr/local/lib/xorg/modules//libvgahw.so > (II) Module vgahw: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 0.1.0 > ABI class: X.Org Video Driver, version 5.0 > (==) intel(0): Depth 24, (--) framebuffer bpp 32 > (==) intel(0): RGB weight 888 > (==) intel(0): Default visual is TrueColor > (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM > (--) intel(0): Chipset: "965GM" > (--) intel(0): Linear framebuffer at 0xE0000000 > (--) intel(0): IO registers at addr 0xFA000000 > (==) intel(0): Using EXA for acceleration > (II) intel(0): 2 display pipes available. > (II) Loading sub module "ddc" > (II) LoadModule: "ddc" > (II) Module "ddc" already built-in > (II) Loading sub module "i2c" > (II) LoadModule: "i2c" > (II) Module "i2c" already built-in > (II) intel(0): Output VGA using monitor section Monitor0 > (II) intel(0): Output LVDS has no monitor section > (II) intel(0): I2C bus "LVDSDDC_C" initialized. > (II) intel(0): Attempting to determine panel fixed mode. > (II) intel(0): I2C device "LVDSDDC_C:E-EDID segment register" registered at address 0x60. > (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. > (II) intel(0): EDID vendor "LEN", prod id 16500 > (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. > (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72. > (II) intel(0): No SDVO device found on SDVOC > (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. > (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. > (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear > (II) intel(0): Resizable framebuffer: not available (1 3) > (II) intel(0): EDID vendor "LEN", prod id 16500 > (II) intel(0): Output VGA disconnected > (II) intel(0): Output LVDS connected > (II) intel(0): Using exact sizes for initial modes > (II) intel(0): Output LVDS using initial mode 1440x900 > (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear > (II) intel(0): detected 512 kB GTT. > (II) intel(0): detected 7676 kB stolen memory. > (==) intel(0): video overlay key set to 0x101fe > (==) intel(0): Will not try to enable page flipping > (==) intel(0): Triple buffering disabled > (==) intel(0): Using gamma correction (1.0, 1.0, 1.0) > (==) intel(0): DPI set to (96, 96) > (II) Loading sub module "fb" > (II) LoadModule: "fb" > (II) Loading /usr/local/lib/xorg/modules//libfb.so > (II) Module fb: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 1.0.0 > ABI class: X.Org ANSI C Emulation, version 0.4 > (II) Loading sub module "exa" > (II) LoadModule: "exa" > (II) Loading /usr/local/lib/xorg/modules//libexa.so > (II) Module exa: vendor="X.Org Foundation" > compiled for 1.6.0, module version = 2.4.0 > ABI class: X.Org Video Driver, version 5.0 > (II) Loading sub module "ramdac" > (II) LoadModule: "ramdac" > (II) Module "ramdac" already built-in > (II) intel(0): Comparing regs from server start up to After PreInit > (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a > (WW) intel(0): PP_STATUS before: on, ready, sequencing idle > (WW) intel(0): PP_STATUS after: on, ready, sequencing on > (==) Depth 24 pixmap format is 32 bpp > (II) do I need RAC? No, I don't. > (II) resource ranges after preInit: > [0] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [1] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [2] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [3] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) > [4] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) > [5] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) > [6] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [7] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > [8] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) > [9] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) > (II) intel(0): Kernel reported 491520 total, 0 used > (II) intel(0): I830CheckAvailableMemory: 1966080 kB available > (WW) intel(0): DRI2 requires UXA > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 11, (OK) > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 11, (OK) > drmOpenByBusid: Searching for BusID pci:0000:00:02.0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 11, (OK) > drmOpenByBusid: drmOpenMinor returns 11 > drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 > (II) [drm] DRM interface version 1.2 > (II) [drm] DRM open master succeeded. > (II) intel(0): [drm] Using the DRM lock SAREA also for drawables. > (II) intel(0): [drm] framebuffer mapped by ddx driver > (II) intel(0): [drm] added 1 reserved context for kernel > (II) intel(0): X context handle = 0x2 > (II) intel(0): [drm] installed DRM signal handler > (**) intel(0): Framebuffer compression disabled > (**) intel(0): Tiling enabled > (==) intel(0): VideoRam: 262144 KB > (II) intel(0): Attempting memory allocation with tiled buffers. > (II) intel(0): Tiled allocation successful. > (II) intel(0): [drm] Registers = 0xfa000000 > (II) intel(0): [drm] ring buffer = 0xe0000000 > (II) intel(0): [drm] mapped front buffer at 0xe012b000, handle = 0xe012b000 > (II) intel(0): [drm] mapped back buffer at 0xe22ec000, handle = 0xe22ec000 > (II) intel(0): [drm] mapped depth buffer at 0xe2b5c000, handle = 0xe2b5c000 > (II) intel(0): [drm] mapped classic textures at 0xe33cc000, handle = 0xe33cc000 > (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432 > (II) intel(0): [dri] visual configs initialized > (II) intel(0): Page Flipping disabled > (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 > (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear > (II) EXA(0): Offscreen pixmap area of 26542080 bytes > (II) EXA(0): Driver registered support for the following operations: > (II) Solid > (II) Copy > (II) Composite (RENDER acceleration) > (==) intel(0): Backing store disabled > (==) intel(0): Silken mouse enabled > (II) intel(0): Initializing HW Cursor > (II) intel(0): [DRI] installation complete > (II) intel(0): xf86BindGARTMemory: bind key 27 at 0x0077f000 (pgoffset 1919) > (II) intel(0): xf86BindGARTMemory: bind key 28 at 0x0099b000 (pgoffset 2459) > (II) intel(0): xf86BindGARTMemory: bind key 29 at 0x022eb000 (pgoffset 8939) > (II) intel(0): xf86BindGARTMemory: bind key 30 at 0x022ec000 (pgoffset 8940) > (II) intel(0): xf86BindGARTMemory: bind key 31 at 0x02b5c000 (pgoffset 11100) > (II) intel(0): xf86BindGARTMemory: bind key 32 at 0x033cc000 (pgoffset 13260) > (II) intel(0): Fixed memory allocation layout: > (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB) > (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB) > (II) intel(0): 0x0002a000-0x00129fff: fake bufmgr (1024 kB) > (II) intel(0): 0x0012a000-0x0012afff: overlay registers (4 kB) > (II) intel(0): 0x0012b000-0x0099afff: front buffer (8640 kB) > (II) intel(0): 0x0077f000: end of stolen memory > (II) intel(0): 0x0099b000-0x022eafff: exa offscreen (25920 kB) > (II) intel(0): 0x022eb000-0x022ebfff: power context (4 kB) > (II) intel(0): 0x022ec000-0x02b5bfff: back buffer (8640 kB) > (II) intel(0): 0x02b5c000-0x033cbfff: depth buffer (8640 kB) > (II) intel(0): 0x033cc000-0x053cbfff: classic textures (32768 kB) > (II) intel(0): 0x10000000: end of aperture > (II) intel(0): using SSC reference clock of 100 MHz > (II) intel(0): Selecting standard 18 bit TMDS pixel format. > (II) intel(0): Output configuration: > (II) intel(0): Pipe A is off > (II) intel(0): Display plane A is now disabled and connected to pipe A. > (II) intel(0): Pipe B is on > (II) intel(0): Display plane B is now enabled and connected to pipe B. > (II) intel(0): Output VGA is connected to pipe none > (II) intel(0): Output LVDS is connected to pipe B > (II) intel(0): [drm] dma control initialized, using IRQ 16 > (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. > (II) intel(0): DPMS enabled > (==) intel(0): Intel XvMC decoder disabled > (II) intel(0): Set up textured video > (II) intel(0): Set up overlay video > (II) intel(0): direct rendering: XF86DRI Enabled > (--) RandR disabled > (II) Initializing built-in extension Generic Event Extension > (II) Initializing built-in extension SHAPE > (II) Initializing built-in extension MIT-SHM > (II) Initializing built-in extension XInputExtension > (II) Initializing built-in extension XTEST > (II) Initializing built-in extension BIG-REQUESTS > (II) Initializing built-in extension SYNC > (II) Initializing built-in extension XKEYBOARD > (II) Initializing built-in extension XC-MISC > (II) Initializing built-in extension XINERAMA > (II) Initializing built-in extension XFIXES > (II) Initializing built-in extension RENDER > (II) Initializing built-in extension RANDR > (II) Initializing built-in extension COMPOSITE > (II) Initializing built-in extension DAMAGE > (II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so > (II) GLX: Initialized DRISWRAST GL provider for screen 0 > (II) intel(0): Setting screen physical size to 287 x 180 > (EE) config/hal: couldn't initialise context: (null) ((null)) > (II) intel(0): xf86UnbindGARTMemory: unbind key 27 > (II) intel(0): xf86UnbindGARTMemory: unbind key 28 > (II) intel(0): xf86UnbindGARTMemory: unbind key 29 > (II) intel(0): xf86UnbindGARTMemory: unbind key 30 > (II) intel(0): xf86UnbindGARTMemory: unbind key 31 > (II) intel(0): xf86UnbindGARTMemory: unbind key 32 > (II) intel(0): [drm] removed 1 reserved context for kernel > (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xfffffffe806d4000 at 0x8006b4000 > (II) intel(0): [drm] Closed DRM master. > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" -- Robert Noland FreeBSD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090515/ec85f6a2/attachment.pgp From sonic2000gr at gmail.com Fri May 15 14:44:02 2009 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Fri May 15 14:44:09 2009 Subject: Xorg on X300 lenovo with 7.2-RELEASE In-Reply-To: <20090515085300.GD30349@macmini.blacquiere.nl> References: <20090515085300.GD30349@macmini.blacquiere.nl> Message-ID: <4A0D7A2F.6050400@gmail.com> Robert Blacquiere wrote: > Hi all, > > I installed a fresh version of FreeBSD 7.2 on my lenovo X300. It was > running OpenBSD for some time. For some reason I can't get Xorg to > display any thing on screen except backlight. In the Xorg.0.log seems no > real issues. I have run freebsd 7.0R with Xorg before without any > problems. I tried also 8.0-CURRENT but it had the same problems so I > tried the 7.2R. They all produce the same backlighted black screen. > > What can I do to get things running, any hints? > > Regards > > Logs and xorg.conf. > > Are you by any chance trying the test with i.e.: X -config /root/xorg.conf.new In the new Xorg this produces a black screen. This is the new 'standard'. Try something like X -config /root/xorg.conf.new -retro (and have a look at the updated handbook section, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html ) From freebsd at blacquiere.nl Fri May 15 15:02:04 2009 From: freebsd at blacquiere.nl (Robert Blacquiere) Date: Fri May 15 15:02:11 2009 Subject: Xorg on X300 lenovo with 7.2-RELEASE In-Reply-To: <4A0D7A2F.6050400@gmail.com> References: <20090515085300.GD30349@macmini.blacquiere.nl> <4A0D7A2F.6050400@gmail.com> Message-ID: <20090515150202.GC31649@macmini.blacquiere.nl> On Fri, May 15, 2009 at 05:20:31PM +0300, Manolis Kiagias wrote: > Robert Blacquiere wrote: > > Hi all, > > > > I installed a fresh version of FreeBSD 7.2 on my lenovo X300. It was > > running OpenBSD for some time. For some reason I can't get Xorg to > > display any thing on screen except backlight. In the Xorg.0.log seems no > > real issues. I have run freebsd 7.0R with Xorg before without any > > problems. I tried also 8.0-CURRENT but it had the same problems so I > > tried the 7.2R. They all produce the same backlighted black screen. > > > > What can I do to get things running, any hints? > > > > Regards > > > > Logs and xorg.conf. > > > > > > Are you by any chance trying the test with i.e.: > > X -config /root/xorg.conf.new > > In the new Xorg this produces a black screen. This is the new 'standard'. > > Try something like X -config /root/xorg.conf.new -retro (and have a look > at the updated handbook section, > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html ) Oh oh seems i'me old school and expected it to behave as my old typewriter :) Thanks for the info and hints, yes it worked of course :) Thanks Regards Robert > From dan at langille.org Fri May 15 21:59:40 2009 From: dan at langille.org (Dan Langille) Date: Fri May 15 21:59:47 2009 Subject: eeePC - disabling tap Message-ID: <4A0DE5C1.3070808@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC 1000HE. Does anyone know how to do that? [1] - when you tap the touchpad, you select or double click on an object. We don't want that. :) Thank you. - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoN5cEACgkQCgsXFM/7nTxyzQCgyyGrfbdSnLtC/KYXIIQrYJ4z 3/AAoMQcyBbQ2hR/YuLoqlg+A4UGw+xb =MppH -----END PGP SIGNATURE----- From onemda at gmail.com Fri May 15 22:27:46 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Fri May 15 22:27:53 2009 Subject: wpa supplicant fails to start In-Reply-To: <49281.80.177.154.53.1242394038.squirrel@sqmail.gn.apc.org> References: <49281.80.177.154.53.1242394038.squirrel@sqmail.gn.apc.org> Message-ID: <3a142e750905151527t4ea63b10tda532c73f0969a72@mail.gmail.com> On 5/15/09, Martin Smith wrote: > >From dmesg: > May 15 13:38:32 lp2 kernel: ath0: mem 0x88000000-0x8800ffff > irq 11 at device 0.0 on cardbus0 > May 15 13:38:32 lp2 kernel: ath0: [ITHREAD] > May 15 13:38:32 lp2 kernel: ath0: AR2417 mac 15.0 RF5424 phy 7.0 > > My wpa_supplicant.conf: > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > network={ > ssid="myssid" > scan_ssid=1 > key_mgmt=WPA-PSK > psk="my wpa secret" > } > > I have put this together using both the handbook and the > wpa_supplicant.conf man page, do I need to add anything else? > > I get this error: > lp2# wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf > ioctl[SIOCG80211, op 98, len 32]: Invalid argument > Failed to initialize driver interface > ELOOP: remaining socket: sock=4 eloop_data=0x28406140 user_data=0x2840d040 > handler=0x8069f50 > > I obviously have something wrong, can anyone point me in the right > direction. > > System is current as of yesterday rebuilt. You mean CURRENT?, in that case you should use wlan0 and not ath0. > Card is TP-Link TL-WN310G > Machine is a Thinkpad X23 > > lp2# ifconfig -a > fxp0: flags=8843 metric 0 mtu 1500 > options=2009 > ether 00:d0:59:b5:a2:0c > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > ath0: flags=8802 metric 0 mtu 2290 > ether 00:23:cd:c5:c3:c9 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > Thanks for any pointers > > > > > -- > Martin > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > -- Paul From onemda at gmail.com Fri May 15 22:31:42 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Fri May 15 22:31:49 2009 Subject: eeePC - disabling tap In-Reply-To: <4A0DE5C1.3070808@langille.org> References: <4A0DE5C1.3070808@langille.org> Message-ID: <3a142e750905151531t5d3f02e1i66bc912ef9cf35e0@mail.gmail.com> On 5/15/09, Dan Langille wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC > 1000HE. Does anyone know how to do that? > > [1] - when you tap the touchpad, you select or double click on an > object. We don't want that. :) > > Thank you. Hmm, that could be done only from a driver side. Dunno if X11 drivers supports such feature but psm(4) provides: hw.psm.tap_timeout: 125000 hw.psm.tap_threshold: 25 > - -- > Dan Langille > > BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ > PGCon - The PostgreSQL Conference: http://www.pgcon.org/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkoN5cEACgkQCgsXFM/7nTxyzQCgyyGrfbdSnLtC/KYXIIQrYJ4z > 3/AAoMQcyBbQ2hR/YuLoqlg+A4UGw+xb > =MppH > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > -- Paul From matheus at eternamente.info Fri May 15 22:44:17 2009 From: matheus at eternamente.info (Nenhum_de_Nos) Date: Fri May 15 22:44:24 2009 Subject: eeePC - disabling tap In-Reply-To: <4A0DE5C1.3070808@langille.org> References: <4A0DE5C1.3070808@langille.org> Message-ID: <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> On Fri, May 15, 2009 18:59, Dan Langille wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC > 1000HE. Does anyone know how to do that? > > [1] - when you tap the touchpad, you select or double click on an > object. We don't want that. :) > > Thank you. > > - -- > Dan Langille quite the opposite, I'd like to enable tap on mine, turion based asus notebook. :) just waiting for the answer to do the opposite :) matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From guru at unixarea.de Sat May 16 06:07:57 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat May 16 06:08:11 2009 Subject: Dell M4400 && Xorg-vesa && 1920x1200 res? In-Reply-To: <1242397462.1755.89.camel@balrog.2hip.net> References: <20090514084617.GA3459@rebelion.Sisis.de> <200905141651.35948.shoesoft@gmx.net> <20090515125250.GA11380@rebelion.Sisis.de> <1242397462.1755.89.camel@balrog.2hip.net> Message-ID: <20090516060753.GA5319@rebelion.Sisis.de> El d?a Friday, May 15, 2009 a las 09:24:22AM -0500, Robert Noland escribi?: > > Yes, this worked; but it was terrible slow on window movements; > > I've got a small fix for the driver x11-drivers/xf86-video-nv and the > > card is now working as it should with the 'nv' module. > > What patch? If it needs review and committing upstream, please send it > to me... > > robert. The mentioned patch is now available in src/nv_driver.c > Thanks for testing this! I'll update the driver with the device names > for the IDs in the 0x065x range tomorrow when it's not 2 am. ;) > You'll be able to point to the patch at [1] then. If you need it > soon, I can push an official release so you don't have to ship a > patched driver. http://cgit.freedesktop.org/xorg/driver/xf86-video-nv/commit/?id=c8d6f7aa7c99a1b71289f8e8e07becc10f61f379 matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From guru at unixarea.de Sat May 16 06:32:51 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat May 16 06:32:58 2009 Subject: CURRENT && HDA Driver Revision: 20090401_0132 && no recording Message-ID: <20090516063246.GA5726@rebelion.Sisis.de> Hello, I can't get to work recording in environment -CURRENT && HDA Driver Revision: 20090401_0132 the sound output is fine in KDE, but as well the KDE mixer does not control it; only with mixer(1) command I can change the volume for example; I've already tried all values for setting $ mixer =rec rdev but nothing helps switching on the micro. The man page of snd_hda(4) explains a lot of device.hints(5) options, but understanding all this is out of my control; I'm attaching a 'dmesg | fgrep hdac'. Any idea how to get recording switched on? I need this for business for Skype... This is the last blocking point to switch over to my new Dell M4400 Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. -------------- next part -------------- May 16 06:16:02 current kernel: hdac0: mem 0xf6fdc000-0xf6fdffff irq 21 at device 27.0 on pci0 May 16 06:16:02 current kernel: hdac0: HDA Driver Revision: 20090401_0132 May 16 06:16:02 current kernel: hdac0: [ITHREAD] May 16 06:16:02 current kernel: hdac0: HDA Codec #0: IDT 92HD71B7 May 16 06:16:02 current kernel: pcm0: at cad 0 nid 1 on hdac0 May 16 06:16:02 current kernel: pcm1: at cad 0 nid 1 on hdac0 May 16 06:16:02 current kernel: pcm2: at cad 0 nid 1 on hdac0 May 16 06:22:15 current kernel: hdac0: mem 0xf6fdc000-0xf6fdffff irq 21 at device 27.0 on pci0 May 16 06:22:15 current kernel: hdac0: HDA Driver Revision: 20090401_0132 May 16 06:22:15 current kernel: hdac0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xf6fdc000 May 16 06:22:15 current kernel: hdac0: attempting to allocate 1 MSI vectors (1 supported) May 16 06:22:15 current kernel: hdac0: using IRQ 257 for MSI May 16 06:22:15 current kernel: hdac0: [MPSAFE] May 16 06:22:15 current kernel: hdac0: [ITHREAD] May 16 06:22:15 current kernel: hdac0: Probing codec #0... May 16 06:22:15 current kernel: hdac0: HDA Codec #0: IDT 92HD71B7 May 16 06:22:15 current kernel: hdac0: HDA Codec ID: 0x111d76b2 May 16 06:22:15 current kernel: hdac0: Vendor: 0x111d May 16 06:22:15 current kernel: hdac0: Device: 0x76b2 May 16 06:22:15 current kernel: hdac0: Revision: 0x03 May 16 06:22:15 current kernel: hdac0: Stepping: 0x02 May 16 06:22:15 current kernel: hdac0: PCI Subvendor: 0x02501028 May 16 06:22:15 current kernel: hdac0: Found audio FG nid=1 startnode=10 endnode=41 total=31 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: Processing audio FG cad=0 nid=1... May 16 06:22:15 current kernel: hdac0: GPIO: 0xc0000008 NumGPIO=8 NumGPO=0 NumGPI=0 GPIWake=1 GPIUnsol=1 May 16 06:22:15 current kernel: hdac0: nid 10 0x0421101f as 1 seq 15 Headphones Jack jack 1 loc 4 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 11 0x04a11021 as 2 seq 1 Mic Jack jack 1 loc 4 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 12 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 May 16 06:22:15 current kernel: hdac0: nid 13 0x90170110 as 1 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1 May 16 06:22:15 current kernel: hdac0: nid 14 0x23a1102e as 2 seq 14 Mic Jack jack 1 loc 35 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 15 0x23011050 as 5 seq 0 Line-out Jack jack 1 loc 35 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 20 0x40f000f2 as 15 seq 2 Other None jack 0 loc 0 color Unknown misc 0 May 16 06:22:15 current kernel: hdac0: nid 24 0x90a601a0 as 10 seq 0 Mic Fixed jack 6 loc 16 color Unknown misc 1 May 16 06:22:15 current kernel: hdac0: nid 25 0x40f000f4 as 15 seq 4 Other None jack 0 loc 0 color Unknown misc 0 May 16 06:22:15 current kernel: hdac0: nid 30 0x014613b0 as 11 seq 0 SPDIF-out Jack jack 6 loc 1 color Black misc 3 May 16 06:22:15 current kernel: hdac0: nid 31 0x40f000f6 as 15 seq 6 Other None jack 0 loc 0 color Unknown misc 0 May 16 06:22:15 current kernel: hdac0: nid 32 0x40f000f7 as 15 seq 7 Other None jack 0 loc 0 color Unknown misc 0 May 16 06:22:15 current kernel: hdac0: nid 39 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 May 16 06:22:15 current kernel: hdac0: Patched pins configuration: May 16 06:22:15 current kernel: hdac0: nid 10 0x0421101f as 1 seq 15 Headphones Jack jack 1 loc 4 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 11 0x04a11021 as 2 seq 1 Mic Jack jack 1 loc 4 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 12 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] May 16 06:22:15 current kernel: hdac0: nid 13 0x90170110 as 1 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1 May 16 06:22:15 current kernel: hdac0: nid 14 0x23a1102e as 2 seq 14 Mic Jack jack 1 loc 35 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 15 0x23011050 as 5 seq 0 Line-out Jack jack 1 loc 35 color Black misc 0 May 16 06:22:15 current kernel: hdac0: nid 20 0x40f000f2 as 15 seq 2 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] May 16 06:22:15 current kernel: hdac0: nid 24 0x90a601a0 as 10 seq 0 Mic Fixed jack 6 loc 16 color Unknown misc 1 May 16 06:22:15 current kernel: hdac0: nid 25 0x40f000f4 as 15 seq 4 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] May 16 06:22:15 current kernel: hdac0: nid 30 0x014613b0 as 11 seq 0 SPDIF-out Jack jack 6 loc 1 color Black misc 3 May 16 06:22:15 current kernel: hdac0: nid 31 0x40f000f6 as 15 seq 6 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] May 16 06:22:15 current kernel: hdac0: nid 32 0x40f000f7 as 15 seq 7 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] May 16 06:22:15 current kernel: hdac0: nid 39 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] May 16 06:22:15 current kernel: hdac0: 5 associations found: May 16 06:22:15 current kernel: hdac0: Association 0 (1) out: May 16 06:22:15 current kernel: hdac0: Pin nid=13 seq=0 May 16 06:22:15 current kernel: hdac0: Pin nid=10 seq=15 May 16 06:22:15 current kernel: hdac0: Association 1 (2) in: May 16 06:22:15 current kernel: hdac0: Pin nid=11 seq=1 May 16 06:22:15 current kernel: hdac0: Pin nid=14 seq=14 May 16 06:22:15 current kernel: hdac0: Association 2 (5) out: May 16 06:22:15 current kernel: hdac0: Pin nid=15 seq=0 May 16 06:22:15 current kernel: hdac0: Association 3 (10) in: May 16 06:22:15 current kernel: hdac0: Pin nid=24 seq=0 May 16 06:22:15 current kernel: hdac0: Association 4 (11) out: May 16 06:22:15 current kernel: hdac0: Pin nid=30 seq=0 May 16 06:22:15 current kernel: hdac0: Tracing association 0 (1) May 16 06:22:15 current kernel: hdac0: Pin 13 traced to DAC 16 May 16 06:22:15 current kernel: hdac0: Pin 10 traced to DAC 16 and hpredir 0 May 16 06:22:15 current kernel: hdac0: Association 0 (1) trace succeeded May 16 06:22:15 current kernel: hdac0: Tracing association 1 (2) May 16 06:22:15 current kernel: hdac0: Pin 11 traced to ADC 18 May 16 06:22:15 current kernel: hdac0: Pin 14 traced to ADC 18 May 16 06:22:15 current kernel: hdac0: Association 1 (2) trace succeeded May 16 06:22:15 current kernel: hdac0: Tracing association 2 (5) May 16 06:22:15 current kernel: hdac0: Pin 15 traced to DAC 17 May 16 06:22:15 current kernel: hdac0: Association 2 (5) trace succeeded May 16 06:22:15 current kernel: hdac0: Tracing association 3 (10) May 16 06:22:15 current kernel: hdac0: Pin 24 traced to ADC 19 May 16 06:22:15 current kernel: hdac0: Association 3 (10) trace succeeded May 16 06:22:15 current kernel: hdac0: Tracing association 4 (11) May 16 06:22:15 current kernel: hdac0: Pin 30 traced to DAC 33 May 16 06:22:15 current kernel: hdac0: Association 4 (11) trace succeeded May 16 06:22:15 current kernel: hdac0: Tracing input monitor May 16 06:22:15 current kernel: hdac0: Tracing nid 23 to out May 16 06:22:15 current kernel: hdac0: nid 23 is input monitor May 16 06:22:15 current kernel: hdac0: Tracing beeper May 16 06:22:15 current kernel: hdac0: Enabling headphone/speaker audio routing switching: May 16 06:22:15 current kernel: hdac0: as=0 sense nid=10 [UNSOL] May 16 06:22:15 current kernel: hdac0: Pin sense: nid=10 res=0x00000000 May 16 06:22:15 current kernel: hdac0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: +-------------------+ May 16 06:22:15 current kernel: hdac0: | DUMPING HDA NODES | May 16 06:22:15 current kernel: hdac0: +-------------------+ May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: Default Parameter May 16 06:22:15 current kernel: hdac0: ----------------- May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000001 May 16 06:22:15 current kernel: hdac0: PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: IN amp: 0x80000000 May 16 06:22:15 current kernel: hdac0: OUT amp: 0x80027f7f May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 10 May 16 06:22:15 current kernel: hdac0: Name: pin: Headphones (Black Jack) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400181 May 16 06:22:15 current kernel: hdac0: UNSOL STEREO May 16 06:22:15 current kernel: hdac0: Association: 0 (0x00008000) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x0000001c May 16 06:22:15 current kernel: hdac0: PDC HP OUT May 16 06:22:15 current kernel: hdac0: Pin config: 0x0421101f May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000080 HP May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=16 [audio output] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=17 [audio output] May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=23 [audio mixer] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 11 May 16 06:22:15 current kernel: hdac0: Name: pin: Mic (Black Jack) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400081 May 16 06:22:15 current kernel: hdac0: UNSOL STEREO May 16 06:22:15 current kernel: hdac0: Association: 1 (0x00000002) May 16 06:22:15 current kernel: hdac0: OSS: mic (mic) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00001724 May 16 06:22:15 current kernel: hdac0: PDC IN VREF[ 50 80 GROUND HIZ ] May 16 06:22:15 current kernel: hdac0: Pin config: 0x04a11021 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000024 IN VREFs May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 12 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: pin: Other (None) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400081 May 16 06:22:15 current kernel: hdac0: UNSOL STEREO May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00001724 May 16 06:22:15 current kernel: hdac0: PDC IN VREF[ 50 80 GROUND HIZ ] May 16 06:22:15 current kernel: hdac0: Pin config: 0x40f000f0 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000000 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 13 May 16 06:22:15 current kernel: hdac0: Name: pin: Speaker (Fixed) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400181 May 16 06:22:15 current kernel: hdac0: UNSOL STEREO May 16 06:22:15 current kernel: hdac0: Association: 0 (0x00000001) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000014 May 16 06:22:15 current kernel: hdac0: PDC OUT May 16 06:22:15 current kernel: hdac0: Pin config: 0x90170110 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000040 OUT May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=16 [audio output] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=17 [audio output] May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=23 [audio mixer] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 14 May 16 06:22:15 current kernel: hdac0: Name: pin: Mic (Black Jack) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400081 May 16 06:22:15 current kernel: hdac0: UNSOL STEREO May 16 06:22:15 current kernel: hdac0: Association: 1 (0x00004000) May 16 06:22:15 current kernel: hdac0: OSS: line (line) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00001724 May 16 06:22:15 current kernel: hdac0: PDC IN VREF[ 50 80 GROUND HIZ ] May 16 06:22:15 current kernel: hdac0: Pin config: 0x23a1102e May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000024 IN VREFs May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 15 May 16 06:22:15 current kernel: hdac0: Name: pin: Line-out (Black Jack) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400181 May 16 06:22:15 current kernel: hdac0: UNSOL STEREO May 16 06:22:15 current kernel: hdac0: Association: 2 (0x00000001) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000014 May 16 06:22:15 current kernel: hdac0: PDC OUT May 16 06:22:15 current kernel: hdac0: Pin config: 0x23011050 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000040 OUT May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=16 [audio output] May 16 06:22:15 current kernel: hdac0: + <- nid=17 [audio output] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=23 [audio mixer] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 16 May 16 06:22:15 current kernel: hdac0: Name: audio output May 16 06:22:15 current kernel: hdac0: Widget cap: 0x000d0c05 May 16 06:22:15 current kernel: hdac0: LRSWAP PWR STEREO May 16 06:22:15 current kernel: hdac0: Association: 0 (0x00008001) May 16 06:22:15 current kernel: hdac0: OSS: pcm (pcm) May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000001 May 16 06:22:15 current kernel: hdac0: PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: Output amp: 0x80027f7f May 16 06:22:15 current kernel: hdac0: mute=1 step=127 size=2 offset=127 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 17 May 16 06:22:15 current kernel: hdac0: Name: audio output May 16 06:22:15 current kernel: hdac0: Widget cap: 0x000d0c05 May 16 06:22:15 current kernel: hdac0: LRSWAP PWR STEREO May 16 06:22:15 current kernel: hdac0: Association: 2 (0x00000001) May 16 06:22:15 current kernel: hdac0: OSS: pcm (pcm) May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000001 May 16 06:22:15 current kernel: hdac0: PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: Output amp: 0x80027f7f May 16 06:22:15 current kernel: hdac0: mute=1 step=127 size=2 offset=127 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 18 May 16 06:22:15 current kernel: hdac0: Name: audio input May 16 06:22:15 current kernel: hdac0: Widget cap: 0x001d0541 May 16 06:22:15 current kernel: hdac0: PWR PROC STEREO May 16 06:22:15 current kernel: hdac0: Association: 1 (0x00004002) May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000001 May 16 06:22:15 current kernel: hdac0: PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: connections: 1 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=28 [audio selector] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 19 May 16 06:22:15 current kernel: hdac0: Name: audio input May 16 06:22:15 current kernel: hdac0: Widget cap: 0x001d0541 May 16 06:22:15 current kernel: hdac0: PWR PROC STEREO May 16 06:22:15 current kernel: hdac0: Association: 3 (0x00000001) May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000001 May 16 06:22:15 current kernel: hdac0: PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: connections: 1 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=29 [audio selector] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 20 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: pin: Other (None) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400100 May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000010 May 16 06:22:15 current kernel: hdac0: OUT May 16 06:22:15 current kernel: hdac0: Pin config: 0x40f000f2 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000000 May 16 06:22:15 current kernel: hdac0: connections: 1 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=22 [audio mixer] [DISABLED] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 21 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00300101 May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=16 [audio output] (selected) May 16 06:22:15 current kernel: hdac0: + <- nid=17 [audio output] May 16 06:22:15 current kernel: hdac0: + <- nid=23 [audio mixer] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 22 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: audio mixer May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00200100 May 16 06:22:15 current kernel: hdac0: connections: 1 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=21 [audio selector] [DISABLED] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 23 May 16 06:22:15 current kernel: hdac0: Name: audio mixer May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0020010b May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: Association: -2 (0x00004002) May 16 06:22:15 current kernel: hdac0: OSS: mix (mix) May 16 06:22:15 current kernel: hdac0: Input amp: 0x80051f17 May 16 06:22:15 current kernel: hdac0: mute=1 step=31 size=5 offset=23 May 16 06:22:15 current kernel: hdac0: connections: 5 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=16 [audio output] May 16 06:22:15 current kernel: hdac0: + <- nid=17 [audio output] May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=39 [pin: Other (None)] [DISABLED] May 16 06:22:15 current kernel: hdac0: + <- nid=26 [audio selector] May 16 06:22:15 current kernel: hdac0: + <- nid=27 [audio selector] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 24 May 16 06:22:15 current kernel: hdac0: Name: pin: Mic (Fixed) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0040000d May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: Association: 3 (0x00000001) May 16 06:22:15 current kernel: hdac0: OSS: monitor (monitor) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000020 May 16 06:22:15 current kernel: hdac0: IN May 16 06:22:15 current kernel: hdac0: Pin config: 0x90a601a0 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000020 IN May 16 06:22:15 current kernel: hdac0: Output amp: 0x00270300 May 16 06:22:15 current kernel: hdac0: mute=0 step=3 size=39 offset=0 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 25 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: pin: Other (None) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0040000d May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000020 May 16 06:22:15 current kernel: hdac0: IN May 16 06:22:15 current kernel: hdac0: Pin config: 0x40f000f4 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000000 May 16 06:22:15 current kernel: hdac0: Output amp: 0x00270300 May 16 06:22:15 current kernel: hdac0: mute=0 step=3 size=39 offset=0 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 26 May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0030010d May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: Association: 1 (0x00004002) May 16 06:22:15 current kernel: hdac0: OSS: line, mic May 16 06:22:15 current kernel: hdac0: Output amp: 0x00270300 May 16 06:22:15 current kernel: hdac0: mute=0 step=3 size=39 offset=0 May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=11 [pin: Mic (Black Jack)] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=12 [pin: Other (None)] [DISABLED] May 16 06:22:15 current kernel: hdac0: + <- nid=14 [pin: Mic (Black Jack)] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 27 May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0030010d May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: Association: 1 (0x00004002) May 16 06:22:15 current kernel: hdac0: OSS: line, mic May 16 06:22:15 current kernel: hdac0: Output amp: 0x00270300 May 16 06:22:15 current kernel: hdac0: mute=0 step=3 size=39 offset=0 May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=11 [pin: Mic (Black Jack)] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=12 [pin: Other (None)] [DISABLED] May 16 06:22:15 current kernel: hdac0: + <- nid=14 [pin: Mic (Black Jack)] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 28 May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0030090d May 16 06:22:15 current kernel: hdac0: LRSWAP STEREO May 16 06:22:15 current kernel: hdac0: Association: 1 (0x00004002) May 16 06:22:15 current kernel: hdac0: OSS: line, mic, mix May 16 06:22:15 current kernel: hdac0: Output amp: 0x80050f00 May 16 06:22:15 current kernel: hdac0: mute=1 step=15 size=5 offset=0 May 16 06:22:15 current kernel: hdac0: connections: 4 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=26 [audio selector] May 16 06:22:15 current kernel: hdac0: + <- nid=23 [audio mixer] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=24 [pin: Mic (Fixed)] May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=25 [pin: Other (None)] [DISABLED] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 29 May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0030090d May 16 06:22:15 current kernel: hdac0: LRSWAP STEREO May 16 06:22:15 current kernel: hdac0: Association: 3 (0x00000001) May 16 06:22:15 current kernel: hdac0: OSS: mix, monitor May 16 06:22:15 current kernel: hdac0: Output amp: 0x80050f00 May 16 06:22:15 current kernel: hdac0: mute=1 step=15 size=5 offset=0 May 16 06:22:15 current kernel: hdac0: connections: 4 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=27 [audio selector] May 16 06:22:15 current kernel: hdac0: + <- nid=23 [audio mixer] May 16 06:22:15 current kernel: hdac0: + <- nid=24 [pin: Mic (Fixed)] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=25 [pin: Other (None)] [DISABLED] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 30 May 16 06:22:15 current kernel: hdac0: Name: pin: SPDIF-out (Black Jack) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400301 May 16 06:22:15 current kernel: hdac0: DIGITAL STEREO May 16 06:22:15 current kernel: hdac0: Association: 4 (0x00000001) May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000010 May 16 06:22:15 current kernel: hdac0: OUT May 16 06:22:15 current kernel: hdac0: Pin config: 0x014613b0 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000040 OUT May 16 06:22:15 current kernel: hdac0: connections: 1 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=36 [audio selector] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 31 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: pin: Other (None) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400701 May 16 06:22:15 current kernel: hdac0: PWR DIGITAL STEREO May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00010010 May 16 06:22:15 current kernel: hdac0: OUT EAPD May 16 06:22:15 current kernel: hdac0: Pin config: 0x40f000f6 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000000 May 16 06:22:15 current kernel: hdac0: EAPD: 0x00000002 May 16 06:22:15 current kernel: hdac0: connections: 2 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=36 [audio selector] (selected) May 16 06:22:15 current kernel: hdac0: + <- nid=37 [audio selector] [DISABLED] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 32 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: pin: Other (None) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400301 May 16 06:22:15 current kernel: hdac0: DIGITAL STEREO May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000010 May 16 06:22:15 current kernel: hdac0: OUT May 16 06:22:15 current kernel: hdac0: Pin config: 0x40f000f7 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000000 May 16 06:22:15 current kernel: hdac0: connections: 1 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=37 [audio selector] [DISABLED] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 33 May 16 06:22:15 current kernel: hdac0: Name: audio output May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00040211 May 16 06:22:15 current kernel: hdac0: DIGITAL STEREO May 16 06:22:15 current kernel: hdac0: Association: 4 (0x00000001) May 16 06:22:15 current kernel: hdac0: OSS: pcm (pcm) May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000005 May 16 06:22:15 current kernel: hdac0: AC3 PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 34 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: audio output May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00040211 May 16 06:22:15 current kernel: hdac0: DIGITAL STEREO May 16 06:22:15 current kernel: hdac0: Stream cap: 0x00000005 May 16 06:22:15 current kernel: hdac0: AC3 PCM May 16 06:22:15 current kernel: hdac0: PCM cap: 0x000e07e0 May 16 06:22:15 current kernel: hdac0: 16 20 24 bits, 44 48 88 96 176 192 KHz May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 35 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: vendor widget May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00f00000 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 36 May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00300101 May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: Association: 4 (0x00000001) May 16 06:22:15 current kernel: hdac0: OSS: pcm May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=33 [audio output] (selected) May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=28 [audio selector] May 16 06:22:15 current kernel: hdac0: + [DISABLED] <- nid=29 [audio selector] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 37 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: audio selector May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00300101 May 16 06:22:15 current kernel: hdac0: STEREO May 16 06:22:15 current kernel: hdac0: connections: 3 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=34 [audio output] [DISABLED] (selected) May 16 06:22:15 current kernel: hdac0: + <- nid=28 [audio selector] May 16 06:22:15 current kernel: hdac0: + <- nid=29 [audio selector] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 38 May 16 06:22:15 current kernel: hdac0: Name: beep widget May 16 06:22:15 current kernel: hdac0: Widget cap: 0x0070000c May 16 06:22:15 current kernel: hdac0: Association: -2 (0x00000000) May 16 06:22:15 current kernel: hdac0: OSS: speaker (speaker) May 16 06:22:15 current kernel: hdac0: Output amp: 0x80170303 May 16 06:22:15 current kernel: hdac0: mute=1 step=3 size=23 offset=3 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 39 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: pin: Other (None) May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00400000 May 16 06:22:15 current kernel: hdac0: Pin cap: 0x00000020 May 16 06:22:15 current kernel: hdac0: IN May 16 06:22:15 current kernel: hdac0: Pin config: 0x40f000f0 May 16 06:22:15 current kernel: hdac0: Pin control: 0x00000000 May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: hdac0: nid: 40 [DISABLED] May 16 06:22:15 current kernel: hdac0: Name: volume widget May 16 06:22:15 current kernel: hdac0: Widget cap: 0x00600000 May 16 06:22:15 current kernel: hdac0: connections: 2 May 16 06:22:15 current kernel: hdac0: | May 16 06:22:15 current kernel: hdac0: + <- nid=16 [audio output] (selected) May 16 06:22:15 current kernel: hdac0: + <- nid=17 [audio output] May 16 06:22:15 current kernel: hdac0: May 16 06:22:15 current kernel: pcm0: at cad 0 nid 1 on hdac0 May 16 06:22:15 current kernel: pcm1: at cad 0 nid 1 on hdac0 May 16 06:22:15 current kernel: pcm2: at cad 0 nid 1 on hdac0 From violet at darkerviolet.com Sat May 16 07:33:30 2009 From: violet at darkerviolet.com (violet@darkerviolet.com) Date: Sat May 16 07:33:38 2009 Subject: Thank you for signing the guestbook Message-ID: <200905160706.n4G76mUs026770@linhost124.prod.mesa1.secureserver.net> Thank you for signing the guestbook! From martinsm at gn.apc.org Sat May 16 11:01:04 2009 From: martinsm at gn.apc.org (Martin Smith) Date: Sat May 16 11:01:10 2009 Subject: wpa supplicant fails to start In-Reply-To: <3a142e750905151527t4ea63b10tda532c73f0969a72@mail.gmail.com> References: <49281.80.177.154.53.1242394038.squirrel@sqmail.gn.apc.org> <3a142e750905151527t4ea63b10tda532c73f0969a72@mail.gmail.com> Message-ID: <4A0E9592.1010400@gn.apc.org> Paul B. Mahol wrote: > On 5/15/09, Martin Smith wrote: >> >From dmesg: >> May 15 13:38:32 lp2 kernel: ath0: mem 0x88000000-0x8800ffff >> irq 11 at device 0.0 on cardbus0 >> May 15 13:38:32 lp2 kernel: ath0: [ITHREAD] >> May 15 13:38:32 lp2 kernel: ath0: AR2417 mac 15.0 RF5424 phy 7.0 >> >> My wpa_supplicant.conf: >> ctrl_interface=/var/run/wpa_supplicant >> ctrl_interface_group=wheel >> network={ >> ssid="myssid" >> scan_ssid=1 >> key_mgmt=WPA-PSK >> psk="my wpa secret" >> } >> >> I have put this together using both the handbook and the >> wpa_supplicant.conf man page, do I need to add anything else? >> >> I get this error: >> lp2# wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf >> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >> Failed to initialize driver interface >> ELOOP: remaining socket: sock=4 eloop_data=0x28406140 user_data=0x2840d040 >> handler=0x8069f50 >> >> I obviously have something wrong, can anyone point me in the right >> direction. >> >> System is current as of yesterday rebuilt. > > You mean CURRENT?, in that case you should use wlan0 and not ath0. Tried that too, just get Failed to onitialize the driver interface. I also tried making an Ndis module, it recognises the card when loaded but the I get a kernel panic and everything grinds to a halt. > >> Card is TP-Link TL-WN310G >> Machine is a Thinkpad X23 >> -- Martin From onemda at gmail.com Sat May 16 11:57:44 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Sat May 16 11:57:50 2009 Subject: wpa supplicant fails to start In-Reply-To: <4A0E9592.1010400@gn.apc.org> References: <49281.80.177.154.53.1242394038.squirrel@sqmail.gn.apc.org> <3a142e750905151527t4ea63b10tda532c73f0969a72@mail.gmail.com> <4A0E9592.1010400@gn.apc.org> Message-ID: <3a142e750905160457l10a35d31qb79d360129fe0d36@mail.gmail.com> On 5/16/09, Martin Smith wrote: > Paul B. Mahol wrote: >> On 5/15/09, Martin Smith wrote: >>> >From dmesg: >>> May 15 13:38:32 lp2 kernel: ath0: mem >>> 0x88000000-0x8800ffff >>> irq 11 at device 0.0 on cardbus0 >>> May 15 13:38:32 lp2 kernel: ath0: [ITHREAD] >>> May 15 13:38:32 lp2 kernel: ath0: AR2417 mac 15.0 RF5424 phy 7.0 >>> >>> My wpa_supplicant.conf: >>> ctrl_interface=/var/run/wpa_supplicant >>> ctrl_interface_group=wheel >>> network={ >>> ssid="myssid" >>> scan_ssid=1 >>> key_mgmt=WPA-PSK >>> psk="my wpa secret" >>> } >>> >>> I have put this together using both the handbook and the >>> wpa_supplicant.conf man page, do I need to add anything else? >>> >>> I get this error: >>> lp2# wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf >>> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >>> Failed to initialize driver interface >>> ELOOP: remaining socket: sock=4 eloop_data=0x28406140 >>> user_data=0x2840d040 >>> handler=0x8069f50 >>> >>> I obviously have something wrong, can anyone point me in the right >>> direction. >>> >>> System is current as of yesterday rebuilt. >> >> You mean CURRENT?, in that case you should use wlan0 and not ath0. > > Tried that too, just get Failed to onitialize the driver interface. > I also tried making an Ndis module, it recognises the card when loaded > but the I get a kernel panic and everything grinds to a halt. You will need to be more specific what you did and what you didn't. What FreeeBSD version are you using? If kernel paniced than it would be very helpfull to provide backtrace and exact way how to reproduce it. >> >>> Card is TP-Link TL-WN310G >>> Machine is a Thinkpad X23 -- Paul From onemda at gmail.com Sat May 16 12:02:55 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Sat May 16 12:03:02 2009 Subject: eeePC - disabling tap In-Reply-To: <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> Message-ID: <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> On 5/16/09, Nenhum_de_Nos wrote: > > On Fri, May 15, 2009 18:59, Dan Langille wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC >> 1000HE. Does anyone know how to do that? >> >> [1] - when you tap the touchpad, you select or double click on an >> object. We don't want that. :) >> >> Thank you. >> >> - -- >> Dan Langille > > quite the opposite, I'd like to enable tap on mine, turion based asus > notebook. :) > > just waiting for the answer to do the opposite :) How is your touchpad detected? Maybe you need to use X11 synaptic driver(guessing). -- Paul From dan at langille.org Sat May 16 15:27:31 2009 From: dan at langille.org (Dan Langille) Date: Sat May 16 15:27:38 2009 Subject: eeePC - disabling tap In-Reply-To: <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> Message-ID: <4A0EDB58.8050809@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul B. Mahol wrote: > On 5/16/09, Nenhum_de_Nos wrote: >> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC >>> 1000HE. Does anyone know how to do that? >>> >>> [1] - when you tap the touchpad, you select or double click on an >>> object. We don't want that. :) >>> >>> Thank you. >>> >>> - -- >>> Dan Langille >> quite the opposite, I'd like to enable tap on mine, turion based asus >> notebook. :) >> >> just waiting for the answer to do the opposite :) > > How is your touchpad detected? from dmesg: psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 > Maybe you need to use X11 synaptic driver(guessing). - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoO21gACgkQCgsXFM/7nTyRygCgzDXS/vE4tqp1OfAT0irtXNHo /dcAn0A94S65G1z3+oXPmk0y9qob2orJ =c/39 -----END PGP SIGNATURE----- From dan at langille.org Sat May 16 16:10:46 2009 From: dan at langille.org (Dan Langille) Date: Sat May 16 16:10:53 2009 Subject: eeePC - disabling tap In-Reply-To: <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> Message-ID: <4A0EE57A.7010909@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul B. Mahol wrote: > On 5/16/09, Nenhum_de_Nos wrote: >> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC >>> 1000HE. Does anyone know how to do that? >>> >>> [1] - when you tap the touchpad, you select or double click on an >>> object. We don't want that. :) >>> >>> Thank you. >>> >>> - -- >>> Dan Langille >> quite the opposite, I'd like to enable tap on mine, turion based asus >> notebook. :) >> >> just waiting for the answer to do the opposite :) > > How is your touchpad detected? > Maybe you need to use X11 synaptic driver(guessing). Following up.... reading http://wiki.freebsd.org/AsusEee under "Touchpad (synaptics) configuration" it says: - - Disable moused in rc.conf - - Add hw.psm.synaptics_support=1 to loader.conf - - pkg_add -r synaptics and edit Xorg.conf according to synaptic's pkg-message I think the package information is out of date. I see no synaptics package. Likely candidates include: x11-drivers/xf86-input-synaptics x11/libsynaptics x11/gsynaptics Only the latter seems to have a pkg-message. I tried that. It (and about 50 other packages) installed cleanly. I altered the mouse input device in /etc/X11/xorg/conf: Section "InputDevice" Identifier "Mouse0" # Driver "mouse" Driver "synaptics" Option "SHMConfig" "on" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection and made the changes contained within/usr/ports/x11/gsynaptics/pkg-message: - - /etc/rc.conf - - /boot/loader.conf - - downside of that is I get no cursor on the console reboot. I see this output from sysctl: hw.psm.synaptics.directional_scrolls: 1 hw.psm.synaptics.low_speed_threshold: 20 hw.psm.synaptics.min_movement: 2 hw.psm.synaptics.squelch_level: 3 I ran gsynaptics and unchecked "enable tapping". I can still tap. Restarted X. Can still tap. I wonder if the init process is failing, because if I run this from the console, I get: $ gsynaptics-init (gsynaptics-init:1097): Gtk-WARNING **: cannot open display: - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoO5XoACgkQCgsXFM/7nTwOCACfXdcu5cr2KOsOyfrS+yXvPtBq k7MAniS97+EPIvcJ35GhV80MH3UbCPNX =+8ye -----END PGP SIGNATURE----- From dan at langille.org Sat May 16 16:34:17 2009 From: dan at langille.org (Dan Langille) Date: Sat May 16 16:34:26 2009 Subject: eeePC - disabling tap In-Reply-To: <4A0EE57A.7010909@langille.org> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> <4A0EE57A.7010909@langille.org> Message-ID: <4A0EEAFE.4070901@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Langille wrote: > Paul B. Mahol wrote: >> On 5/16/09, Nenhum_de_Nos wrote: >>> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC >>>> 1000HE. Does anyone know how to do that? >>>> >>>> [1] - when you tap the touchpad, you select or double click on an >>>> object. We don't want that. :) >>>> >>>> Thank you. >>>> >>>> - -- >>>> Dan Langille >>> quite the opposite, I'd like to enable tap on mine, turion based asus >>> notebook. :) >>> >>> just waiting for the answer to do the opposite :) >> How is your touchpad detected? >> Maybe you need to use X11 synaptic driver(guessing). > > Following up.... reading http://wiki.freebsd.org/AsusEee under "Touchpad > (synaptics) configuration" it says: > > - Disable moused in rc.conf > - Add hw.psm.synaptics_support=1 to loader.conf > - pkg_add -r synaptics and edit Xorg.conf according to synaptic's > pkg-message > > I think the package information is out of date. I see no synaptics > package. Likely candidates include: > > x11-drivers/xf86-input-synaptics > x11/libsynaptics > x11/gsynaptics > > Only the latter seems to have a pkg-message. I tried that. It (and > about 50 other packages) installed cleanly. > > I altered the mouse input device in /etc/X11/xorg/conf: > > Section "InputDevice" > Identifier "Mouse0" > # Driver "mouse" > Driver "synaptics" > Option "SHMConfig" "on" > > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > and made the changes contained within/usr/ports/x11/gsynaptics/pkg-message: > > - /etc/rc.conf > - /boot/loader.conf > - downside of that is I get no cursor on the console > > reboot. > > I see this output from sysctl: > > hw.psm.synaptics.directional_scrolls: 1 > hw.psm.synaptics.low_speed_threshold: 20 > hw.psm.synaptics.min_movement: 2 > hw.psm.synaptics.squelch_level: 3 > > I ran gsynaptics and unchecked "enable tapping". I can still tap. > Restarted X. Can still tap. > > I wonder if the init process is failing, because if I run this from the > console, I get: > > $ gsynaptics-init > > (gsynaptics-init:1097): Gtk-WARNING **: cannot open display: Interesting bits from /var/log/Xorg.0.log (II) No default mouse found, adding one (**) |-->Input Device "" (II) Synaptics touchpad driver version 0.99.3 (**) Option "Device" "/dev/sysmouse" (**) Option "SHMConfig" "on" Query no Synaptics: 000000 (--) Mouse0: no supported touchpad found (**) Option "CorePointer" (**) Mouse0: always reports core events (II) XINPUT: Adding extended input device "Mouse0" (type: TOUCHPAD) (**) Mouse0: (accel) keeping acceleration scheme 1 (**) Mouse0: (accel) filter chain progression: 2.00 (**) Mouse0: (accel) filter stage 0: 20.00 ms (**) Mouse0: (accel) set acceleration profile 0 Query no Synaptics: 000000 (--) Mouse0: no supported touchpad found - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoO6v0ACgkQCgsXFM/7nTxaWwCgn7dYtvWnQm+vY4UWndKN/nOy bJgAn3T2h9WzI6XAn2W4d5zYOqLcc3UQ =3v3U -----END PGP SIGNATURE----- From onemda at gmail.com Sat May 16 17:18:38 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Sat May 16 17:18:45 2009 Subject: eeePC - disabling tap In-Reply-To: <4A0EEAFE.4070901@langille.org> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> <4A0EE57A.7010909@langille.org> <4A0EEAFE.4070901@langille.org> Message-ID: <3a142e750905161018y7d0921f8s409956c941c13ed5@mail.gmail.com> On 5/16/09, Dan Langille wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dan Langille wrote: >> Paul B. Mahol wrote: >>> On 5/16/09, Nenhum_de_Nos wrote: >>>> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> Folks: I wish to disable the tap feature[1] for the touchpad on an >>>>> EeePC >>>>> 1000HE. Does anyone know how to do that? >>>>> >>>>> [1] - when you tap the touchpad, you select or double click on an >>>>> object. We don't want that. :) >>>>> >>>>> Thank you. >>>>> >>>>> - -- >>>>> Dan Langille >>>> quite the opposite, I'd like to enable tap on mine, turion based asus >>>> notebook. :) >>>> >>>> just waiting for the answer to do the opposite :) >>> How is your touchpad detected? >>> Maybe you need to use X11 synaptic driver(guessing). >> >> Following up.... reading http://wiki.freebsd.org/AsusEee under "Touchpad >> (synaptics) configuration" it says: >> >> - Disable moused in rc.conf >> - Add hw.psm.synaptics_support=1 to loader.conf >> - pkg_add -r synaptics and edit Xorg.conf according to synaptic's >> pkg-message >> >> I think the package information is out of date. I see no synaptics >> package. Likely candidates include: >> >> x11-drivers/xf86-input-synaptics >> x11/libsynaptics >> x11/gsynaptics >> >> Only the latter seems to have a pkg-message. I tried that. It (and >> about 50 other packages) installed cleanly. >> >> I altered the mouse input device in /etc/X11/xorg/conf: >> >> Section "InputDevice" >> Identifier "Mouse0" >> # Driver "mouse" >> Driver "synaptics" >> Option "SHMConfig" "on" >> >> Option "Protocol" "auto" >> Option "Device" "/dev/sysmouse" >> Option "ZAxisMapping" "4 5 6 7" >> EndSection >> >> and made the changes contained >> within/usr/ports/x11/gsynaptics/pkg-message: >> >> - /etc/rc.conf >> - /boot/loader.conf >> - downside of that is I get no cursor on the console In console mouse can only work via moused(8) & sysmouse(4) combination using syscons(4). Probbably psm(4) could have sysctl "tapping_disabled" feature implemented for synaptics case. >> >> reboot. >> >> I see this output from sysctl: >> >> hw.psm.synaptics.directional_scrolls: 1 >> hw.psm.synaptics.low_speed_threshold: 20 >> hw.psm.synaptics.min_movement: 2 >> hw.psm.synaptics.squelch_level: 3 >> >> I ran gsynaptics and unchecked "enable tapping". I can still tap. >> Restarted X. Can still tap. >> >> I wonder if the init process is failing, because if I run this from the >> console, I get: >> >> $ gsynaptics-init >> >> (gsynaptics-init:1097): Gtk-WARNING **: cannot open display: > > Interesting bits from /var/log/Xorg.0.log > > > (II) No default mouse found, adding one > (**) |-->Input Device "" > > > (II) Synaptics touchpad driver version 0.99.3 > (**) Option "Device" "/dev/sysmouse" > (**) Option "SHMConfig" "on" > Query no Synaptics: 000000 > (--) Mouse0: no supported touchpad found > (**) Option "CorePointer" > (**) Mouse0: always reports core events > (II) XINPUT: Adding extended input device "Mouse0" (type: TOUCHPAD) > (**) Mouse0: (accel) keeping acceleration scheme 1 > (**) Mouse0: (accel) filter chain progression: 2.00 > (**) Mouse0: (accel) filter stage 0: 20.00 ms > (**) Mouse0: (accel) set acceleration profile 0 > Query no Synaptics: 000000 > (--) Mouse0: no supported touchpad found It looks to me that HAL is doing its job :) > - -- > Dan Langille > > BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ > PGCon - The PostgreSQL Conference: http://www.pgcon.org/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.11 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkoO6v0ACgkQCgsXFM/7nTxaWwCgn7dYtvWnQm+vY4UWndKN/nOy > bJgAn3T2h9WzI6XAn2W4d5zYOqLcc3UQ > =3v3U > -----END PGP SIGNATURE----- > -- Paul From dan at langille.org Sat May 16 17:42:46 2009 From: dan at langille.org (Dan Langille) Date: Sat May 16 17:42:53 2009 Subject: eeePC - disabling tap In-Reply-To: <3a142e750905161018y7d0921f8s409956c941c13ed5@mail.gmail.com> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> <4A0EE57A.7010909@langille.org> <4A0EEAFE.4070901@langille.org> <3a142e750905161018y7d0921f8s409956c941c13ed5@mail.gmail.com> Message-ID: <4A0EFB0A.6020309@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul B. Mahol wrote: > On 5/16/09, Dan Langille wrote: > Dan Langille wrote: >>>> Paul B. Mahol wrote: >>>>> On 5/16/09, Nenhum_de_Nos wrote: >>>>>> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>> Hash: SHA1 >>>>>>> >>>>>>> Folks: I wish to disable the tap feature[1] for the touchpad on an >>>>>>> EeePC >>>>>>> 1000HE. Does anyone know how to do that? >>>>>>> >>>>>>> [1] - when you tap the touchpad, you select or double click on an >>>>>>> object. We don't want that. :) >>>>>>> >>>>>>> Thank you. >>>>>>> >>>>>>> - -- >>>>>>> Dan Langille >>>>>> quite the opposite, I'd like to enable tap on mine, turion based asus >>>>>> notebook. :) >>>>>> >>>>>> just waiting for the answer to do the opposite :) >>>>> How is your touchpad detected? >>>>> Maybe you need to use X11 synaptic driver(guessing). >>>> Following up.... reading http://wiki.freebsd.org/AsusEee under "Touchpad >>>> (synaptics) configuration" it says: >>>> >>>> - Disable moused in rc.conf >>>> - Add hw.psm.synaptics_support=1 to loader.conf >>>> - pkg_add -r synaptics and edit Xorg.conf according to synaptic's >>>> pkg-message >>>> >>>> I think the package information is out of date. I see no synaptics >>>> package. Likely candidates include: >>>> >>>> x11-drivers/xf86-input-synaptics >>>> x11/libsynaptics >>>> x11/gsynaptics >>>> >>>> Only the latter seems to have a pkg-message. I tried that. It (and >>>> about 50 other packages) installed cleanly. >>>> >>>> I altered the mouse input device in /etc/X11/xorg/conf: >>>> >>>> Section "InputDevice" >>>> Identifier "Mouse0" >>>> # Driver "mouse" >>>> Driver "synaptics" >>>> Option "SHMConfig" "on" >>>> >>>> Option "Protocol" "auto" >>>> Option "Device" "/dev/sysmouse" >>>> Option "ZAxisMapping" "4 5 6 7" >>>> EndSection >>>> >>>> and made the changes contained >>>> within/usr/ports/x11/gsynaptics/pkg-message: >>>> >>>> - /etc/rc.conf >>>> - /boot/loader.conf >>>> - downside of that is I get no cursor on the console > >> In console mouse can only work via moused(8) & sysmouse(4) combination >> using syscons(4). >> Probbably psm(4) could have sysctl "tapping_disabled" feature implemented >> for synaptics case. > >>>> reboot. >>>> >>>> I see this output from sysctl: >>>> >>>> hw.psm.synaptics.directional_scrolls: 1 >>>> hw.psm.synaptics.low_speed_threshold: 20 >>>> hw.psm.synaptics.min_movement: 2 >>>> hw.psm.synaptics.squelch_level: 3 >>>> >>>> I ran gsynaptics and unchecked "enable tapping". I can still tap. >>>> Restarted X. Can still tap. >>>> >>>> I wonder if the init process is failing, because if I run this from the >>>> console, I get: >>>> >>>> $ gsynaptics-init >>>> >>>> (gsynaptics-init:1097): Gtk-WARNING **: cannot open display: > Interesting bits from /var/log/Xorg.0.log > > > (II) No default mouse found, adding one > (**) |-->Input Device "" > > > (II) Synaptics touchpad driver version 0.99.3 > (**) Option "Device" "/dev/sysmouse" > (**) Option "SHMConfig" "on" > Query no Synaptics: 000000 > (--) Mouse0: no supported touchpad found > (**) Option "CorePointer" > (**) Mouse0: always reports core events > (II) XINPUT: Adding extended input device "Mouse0" (type: TOUCHPAD) > (**) Mouse0: (accel) keeping acceleration scheme 1 > (**) Mouse0: (accel) filter chain progression: 2.00 > (**) Mouse0: (accel) filter stage 0: 20.00 ms > (**) Mouse0: (accel) set acceleration profile 0 > Query no Synaptics: 000000 > (--) Mouse0: no supported touchpad found > >> It looks to me that HAL is doing its job :) Hmmm, well, I still can't disable tap.:) - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoO+woACgkQCgsXFM/7nTwocgCfRYUhd9J9AfgSynIpzaozF5Fv Bf8AmgL+ECITAn0JbHRqQ2FfZEU8EgBV =B/hv -----END PGP SIGNATURE----- From onemda at gmail.com Sat May 16 17:44:39 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Sat May 16 17:44:46 2009 Subject: eeePC - disabling tap In-Reply-To: <3a142e750905161018y7d0921f8s409956c941c13ed5@mail.gmail.com> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> <4A0EE57A.7010909@langille.org> <4A0EEAFE.4070901@langille.org> <3a142e750905161018y7d0921f8s409956c941c13ed5@mail.gmail.com> Message-ID: <3a142e750905161044i3ca51effs27f24c7e9f6540fc@mail.gmail.com> On 5/16/09, Paul B. Mahol wrote: > On 5/16/09, Dan Langille wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Dan Langille wrote: >>> Paul B. Mahol wrote: >>>> On 5/16/09, Nenhum_de_Nos wrote: >>>>> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>> Hash: SHA1 >>>>>> >>>>>> Folks: I wish to disable the tap feature[1] for the touchpad on an >>>>>> EeePC >>>>>> 1000HE. Does anyone know how to do that? >>>>>> >>>>>> [1] - when you tap the touchpad, you select or double click on an >>>>>> object. We don't want that. :) >>>>>> >>>>>> Thank you. >>>>>> >>>>>> - -- >>>>>> Dan Langille >>>>> quite the opposite, I'd like to enable tap on mine, turion based asus >>>>> notebook. :) >>>>> >>>>> just waiting for the answer to do the opposite :) >>>> How is your touchpad detected? >>>> Maybe you need to use X11 synaptic driver(guessing). >>> >>> Following up.... reading http://wiki.freebsd.org/AsusEee under "Touchpad >>> (synaptics) configuration" it says: >>> >>> - Disable moused in rc.conf >>> - Add hw.psm.synaptics_support=1 to loader.conf >>> - pkg_add -r synaptics and edit Xorg.conf according to synaptic's >>> pkg-message >>> >>> I think the package information is out of date. I see no synaptics >>> package. Likely candidates include: >>> >>> x11-drivers/xf86-input-synaptics >>> x11/libsynaptics >>> x11/gsynaptics >>> >>> Only the latter seems to have a pkg-message. I tried that. It (and >>> about 50 other packages) installed cleanly. >>> >>> I altered the mouse input device in /etc/X11/xorg/conf: >>> >>> Section "InputDevice" >>> Identifier "Mouse0" >>> # Driver "mouse" >>> Driver "synaptics" >>> Option "SHMConfig" "on" >>> >>> Option "Protocol" "auto" >>> Option "Device" "/dev/sysmouse" >>> Option "ZAxisMapping" "4 5 6 7" >>> EndSection >>> >>> and made the changes contained >>> within/usr/ports/x11/gsynaptics/pkg-message: >>> >>> - /etc/rc.conf >>> - /boot/loader.conf >>> - downside of that is I get no cursor on the console > > In console mouse can only work via moused(8) & sysmouse(4) combination > using syscons(4). > Probbably psm(4) could have sysctl "tapping_disabled" feature implemented > for synaptics case. > >>> >>> reboot. >>> >>> I see this output from sysctl: >>> >>> hw.psm.synaptics.directional_scrolls: 1 >>> hw.psm.synaptics.low_speed_threshold: 20 >>> hw.psm.synaptics.min_movement: 2 >>> hw.psm.synaptics.squelch_level: 3 >>> >>> I ran gsynaptics and unchecked "enable tapping". I can still tap. >>> Restarted X. Can still tap. >>> >>> I wonder if the init process is failing, because if I run this from the >>> console, I get: >>> >>> $ gsynaptics-init >>> >>> (gsynaptics-init:1097): Gtk-WARNING **: cannot open display: >> >> Interesting bits from /var/log/Xorg.0.log >> >> >> (II) No default mouse found, adding one >> (**) |-->Input Device "" >> >> >> (II) Synaptics touchpad driver version 0.99.3 >> (**) Option "Device" "/dev/sysmouse" >> (**) Option "SHMConfig" "on" >> Query no Synaptics: 000000 >> (--) Mouse0: no supported touchpad found >> (**) Option "CorePointer" >> (**) Mouse0: always reports core events >> (II) XINPUT: Adding extended input device "Mouse0" (type: TOUCHPAD) >> (**) Mouse0: (accel) keeping acceleration scheme 1 >> (**) Mouse0: (accel) filter chain progression: 2.00 >> (**) Mouse0: (accel) filter stage 0: 20.00 ms >> (**) Mouse0: (accel) set acceleration profile 0 >> Query no Synaptics: 000000 >> (--) Mouse0: no supported touchpad found > > It looks to me that HAL is doing its job :) > >> - -- >> Dan Langille >> >> BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ >> PGCon - The PostgreSQL Conference: http://www.pgcon.org/ >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.11 (FreeBSD) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iEYEARECAAYFAkoO6v0ACgkQCgsXFM/7nTxaWwCgn7dYtvWnQm+vY4UWndKN/nOy >> bJgAn3T2h9WzI6XAn2W4d5zYOqLcc3UQ >> =3v3U >> -----END PGP SIGNATURE----- >> Well I tried it myself and it works(more or less), I dont like touchpad precision ... add "hw.psm.synaptics_support=1" to /boot/loader.conf and reboot, (oh why this is not plug and play , should be reported as bug, so that rebooting is not required) install xf86-input-synaptics, disable moused, and edit xorg.conf(mine is with HAL disabled during compile): Section "InputDevice" Identifier "Mouse1" Driver "synaptics" Option "Protocol" "psm" Option "Device" "/dev/psm0" Option "TouchpadOff" "2" EndSection Now only replace Mouse0 with Mouse1 in your xorg.conf in right Section ;) Dunno what HAL may do if you compiled Xorg with it, in that case you should have xorg.conf completly removed.... and HAL should be smart enough to do this on its own way. Going to undo this soon ... I prefer sysmouse(4)/moused(4) combo. -- Paul From dan at langille.org Sat May 16 17:56:35 2009 From: dan at langille.org (Dan Langille) Date: Sat May 16 17:56:41 2009 Subject: eeePC - disabling tap In-Reply-To: <3a142e750905161044i3ca51effs27f24c7e9f6540fc@mail.gmail.com> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> <4A0EE57A.7010909@langille.org> <4A0EEAFE.4070901@langille.org> <3a142e750905161018y7d0921f8s409956c941c13ed5@mail.gmail.com> <3a142e750905161044i3ca51effs27f24c7e9f6540fc@mail.gmail.com> Message-ID: <4A0EFE41.5020705@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul B. Mahol wrote: > On 5/16/09, Paul B. Mahol wrote: >> On 5/16/09, Dan Langille wrote: > Dan Langille wrote: >>>>> Paul B. Mahol wrote: >>>>>> On 5/16/09, Nenhum_de_Nos wrote: >>>>>>> On Fri, May 15, 2009 18:59, Dan Langille wrote: >>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>>>>> Hash: SHA1 >>>>>>>> >>>>>>>> Folks: I wish to disable the tap feature[1] for the touchpad on an >>>>>>>> EeePC >>>>>>>> 1000HE. Does anyone know how to do that? >>>>>>>> >>>>>>>> [1] - when you tap the touchpad, you select or double click on an >>>>>>>> object. We don't want that. :) >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> - -- >>>>>>>> Dan Langille >>>>>>> quite the opposite, I'd like to enable tap on mine, turion based asus >>>>>>> notebook. :) >>>>>>> >>>>>>> just waiting for the answer to do the opposite :) >>>>>> How is your touchpad detected? >>>>>> Maybe you need to use X11 synaptic driver(guessing). >>>>> Following up.... reading http://wiki.freebsd.org/AsusEee under "Touchpad >>>>> (synaptics) configuration" it says: >>>>> >>>>> - Disable moused in rc.conf >>>>> - Add hw.psm.synaptics_support=1 to loader.conf >>>>> - pkg_add -r synaptics and edit Xorg.conf according to synaptic's >>>>> pkg-message >>>>> >>>>> I think the package information is out of date. I see no synaptics >>>>> package. Likely candidates include: >>>>> >>>>> x11-drivers/xf86-input-synaptics >>>>> x11/libsynaptics >>>>> x11/gsynaptics >>>>> >>>>> Only the latter seems to have a pkg-message. I tried that. It (and >>>>> about 50 other packages) installed cleanly. >>>>> >>>>> I altered the mouse input device in /etc/X11/xorg/conf: >>>>> >>>>> Section "InputDevice" >>>>> Identifier "Mouse0" >>>>> # Driver "mouse" >>>>> Driver "synaptics" >>>>> Option "SHMConfig" "on" >>>>> >>>>> Option "Protocol" "auto" >>>>> Option "Device" "/dev/sysmouse" >>>>> Option "ZAxisMapping" "4 5 6 7" >>>>> EndSection >>>>> >>>>> and made the changes contained >>>>> within/usr/ports/x11/gsynaptics/pkg-message: >>>>> >>>>> - /etc/rc.conf >>>>> - /boot/loader.conf >>>>> - downside of that is I get no cursor on the console >>> In console mouse can only work via moused(8) & sysmouse(4) combination >>> using syscons(4). >>> Probbably psm(4) could have sysctl "tapping_disabled" feature implemented >>> for synaptics case. >>> >>>>> reboot. >>>>> >>>>> I see this output from sysctl: >>>>> >>>>> hw.psm.synaptics.directional_scrolls: 1 >>>>> hw.psm.synaptics.low_speed_threshold: 20 >>>>> hw.psm.synaptics.min_movement: 2 >>>>> hw.psm.synaptics.squelch_level: 3 >>>>> >>>>> I ran gsynaptics and unchecked "enable tapping". I can still tap. >>>>> Restarted X. Can still tap. >>>>> >>>>> I wonder if the init process is failing, because if I run this from the >>>>> console, I get: >>>>> >>>>> $ gsynaptics-init >>>>> >>>>> (gsynaptics-init:1097): Gtk-WARNING **: cannot open display: > Interesting bits from /var/log/Xorg.0.log > > > (II) No default mouse found, adding one > (**) |-->Input Device "" > > > (II) Synaptics touchpad driver version 0.99.3 > (**) Option "Device" "/dev/sysmouse" > (**) Option "SHMConfig" "on" > Query no Synaptics: 000000 > (--) Mouse0: no supported touchpad found > (**) Option "CorePointer" > (**) Mouse0: always reports core events > (II) XINPUT: Adding extended input device "Mouse0" (type: TOUCHPAD) > (**) Mouse0: (accel) keeping acceleration scheme 1 > (**) Mouse0: (accel) filter chain progression: 2.00 > (**) Mouse0: (accel) filter stage 0: 20.00 ms > (**) Mouse0: (accel) set acceleration profile 0 > Query no Synaptics: 000000 > (--) Mouse0: no supported touchpad found >>> It looks to me that HAL is doing its job :) >>> >>> > Well I tried it myself and it works(more or less), I dont like > touchpad precision ... > add "hw.psm.synaptics_support=1" to /boot/loader.conf and reboot, (oh > why this is not plug and play > , should be reported as bug, so that rebooting is not required) > install xf86-input-synaptics, disable moused, and edit xorg.conf(mine > is with HAL disabled during compile): > Section "InputDevice" > Identifier "Mouse1" > Driver "synaptics" > Option "Protocol" "psm" > Option "Device" "/dev/psm0" > Option "TouchpadOff" "2" > EndSection > Now only replace Mouse0 with Mouse1 in your xorg.conf in right Section ;) > Dunno what HAL may do if you compiled Xorg with it, > in that case you should have xorg.conf completly removed.... > and HAL should be smart enough to do this on its own way. > Going to undo this soon ... I prefer sysmouse(4)/moused(4) combo. I can confirm, this disables the touch pad. :) Perhaps I should just buy my mother an external mouse. - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoO/kEACgkQCgsXFM/7nTzOzgCdGGSw9Kn3qkOh9N64LHul4XvQ DQMAoPlahO3ZSpPtI8FqOaU9RCmvup3U =XCg4 -----END PGP SIGNATURE----- From martinsm at gn.apc.org Sat May 16 19:31:20 2009 From: martinsm at gn.apc.org (Martin Smith) Date: Sat May 16 19:31:28 2009 Subject: wpa supplicant fails to start In-Reply-To: <3a142e750905160457l10a35d31qb79d360129fe0d36@mail.gmail.com> References: <49281.80.177.154.53.1242394038.squirrel@sqmail.gn.apc.org> <3a142e750905151527t4ea63b10tda532c73f0969a72@mail.gmail.com> <4A0E9592.1010400@gn.apc.org> <3a142e750905160457l10a35d31qb79d360129fe0d36@mail.gmail.com> Message-ID: <4A0F147F.1080405@gn.apc.org> Paul B. Mahol wrote: > On 5/16/09, Martin Smith wrote: >> Paul B. Mahol wrote: >>> On 5/15/09, Martin Smith wrote: >>>> >From dmesg: >>>> May 15 13:38:32 lp2 kernel: ath0: mem >>>> 0x88000000-0x8800ffff >>>> irq 11 at device 0.0 on cardbus0 >>>> May 15 13:38:32 lp2 kernel: ath0: [ITHREAD] >>>> May 15 13:38:32 lp2 kernel: ath0: AR2417 mac 15.0 RF5424 phy 7.0 >>>> >>>> My wpa_supplicant.conf: >>>> ctrl_interface=/var/run/wpa_supplicant >>>> ctrl_interface_group=wheel >>>> network={ >>>> ssid="myssid" >>>> scan_ssid=1 >>>> key_mgmt=WPA-PSK >>>> psk="my wpa secret" >>>> } >>>> >>>> I have put this together using both the handbook and the >>>> wpa_supplicant.conf man page, do I need to add anything else? >>>> >>>> I get this error: >>>> lp2# wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf >>>> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >>>> Failed to initialize driver interface >>>> ELOOP: remaining socket: sock=4 eloop_data=0x28406140 >>>> user_data=0x2840d040 >>>> handler=0x8069f50 >>>> >>>> I obviously have something wrong, can anyone point me in the right >>>> direction. >>>> >>>> System is current as of yesterday rebuilt. >>> You mean CURRENT?, in that case you should use wlan0 and not ath0. >> Tried that too, just get Failed to onitialize the driver interface. >> I also tried making an Ndis module, it recognises the card when loaded >> but the I get a kernel panic and everything grinds to a halt. > > You will need to be more specific what you did and what you didn't. > > What FreeeBSD version are you using? > > If kernel paniced than it would be very helpfull to provide > backtrace and exact way how to reproduce it. I will do that and post results in a day or so, thanks. -- Martin From dan at langille.org Sat May 16 20:53:06 2009 From: dan at langille.org (Dan Langille) Date: Sat May 16 20:53:13 2009 Subject: eeePC - disabling tap In-Reply-To: <4A0DE5C1.3070808@langille.org> References: <4A0DE5C1.3070808@langille.org> Message-ID: <4A0F27A0.8010500@langille.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Langille wrote: > Folks: I wish to disable the tap feature[1] for the touchpad on an EeePC > 1000HE. Does anyone know how to do that? > > [1] - when you tap the touchpad, you select or double click on an > object. We don't want that. :) FWIW, I've abandoned this goal. I've bought my mom a USB wireless mouse instead and disabled the touchpad. - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoPJ6AACgkQCgsXFM/7nTxTyQCeMGEp8ZdbhAZIYLqRhrBHkalM hFkAnjhzx0FMCUz3EInLRHOZAe6m3h8f =WqUS -----END PGP SIGNATURE----- From mav at FreeBSD.org Sat May 16 21:36:59 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sat May 16 21:37:11 2009 Subject: CURRENT && HDA Driver Revision: 20090401_0132 && no recording In-Reply-To: <1242469381.00112742.1242456003@10.7.7.3> References: <1242469381.00112742.1242456003@10.7.7.3> Message-ID: <4A0F31F0.8090601@FreeBSD.org> Matthias Apitz wrote: > I can't get to work recording in environment -CURRENT && HDA Driver > Revision: 20090401_0132 > > the sound output is fine in KDE, but as well the KDE mixer does > not control it; only with mixer(1) command I can change the volume for > example; I've already tried all values for setting > > $ mixer =rec rdev > > but nothing helps switching on the micro. The man page of snd_hda(4) > explains a lot of device.hints(5) options, but understanding all this is > out of my control; I'm attaching a 'dmesg | fgrep hdac'. > > Any idea how to get recording switched on? I need this for business for > Skype... This is the last blocking point to switch over to my new Dell > M4400 You have 3 recording sources available via 2 pcm devices. As I can see, your built-in mic assigned to pcm1 device. Have you tried to record from pcm1? PS: `dmesg | fgrep pcm` is also interesting. -- Alexander Motin From guru at unixarea.de Sun May 17 07:19:45 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sun May 17 07:19:57 2009 Subject: CURRENT && HDA Driver Revision: 20090401_0132 && no recording In-Reply-To: <4A0F31F0.8090601@FreeBSD.org> References: <1242469381.00112742.1242456003@10.7.7.3> <4A0F31F0.8090601@FreeBSD.org> Message-ID: <20090517091947.GA2887@current.Sisis.de> El d?a Sunday, May 17, 2009 a las 12:36:48AM +0300, Alexander Motin escribi?: > Matthias Apitz wrote: > >I can't get to work recording in environment -CURRENT && HDA Driver > >Revision: 20090401_0132 > > > >the sound output is fine in KDE, but as well the KDE mixer does > >not control it; only with mixer(1) command I can change the volume for > >example; I've already tried all values for setting > > > >$ mixer =rec rdev > > > >but nothing helps switching on the micro. The man page of snd_hda(4) > >explains a lot of device.hints(5) options, but understanding all this is > >out of my control; I'm attaching a 'dmesg | fgrep hdac'. > > > >Any idea how to get recording switched on? I need this for business for > >Skype... This is the last blocking point to switch over to my new Dell > >M4400 btw: I have now already moved all my userland to the M4400; > > You have 3 recording sources available via 2 pcm devices. As I can see, > your built-in mic assigned to pcm1 device. Have you tried to record from > pcm1? It was even more simple. I was only thinking that recording was not working because I could not hear my own voice while speaking in the headset (what I can hear for example in the EeePC 900 using snd_hda too); that's why I did not tried the Echo Service of Skype; later on I did tried it and it records fine from 'mic': # mixer Mixer vol is currently set to 83:83 Mixer pcm is currently set to 100:100 Mixer speaker is currently set to 100:100 Mixer mix is currently set to 100:100 Mixer rec is currently set to 100:100 Recording source: mic > > PS: `dmesg | fgrep pcm` is also interesting. # dmesg | fgrep pcm pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 pcm2: at cad 0 nid 1 on hdac0 The last (non blocking) problem is to get support for the Wifi card: EMEA Intel Pro Wireless WI-FI 5100 (802.11a/g/ Draft-n) or replace it by some other card (the card is a plug-in card and can be changed by the user in the laptop). Thanks for your reply in any case. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From sarawgi.aditya at gmail.com Sun May 17 14:50:54 2009 From: sarawgi.aditya at gmail.com (Aditya Sarawgi) Date: Sun May 17 14:51:01 2009 Subject: FreeBSD on Dell Studio 15 In-Reply-To: References: <20090427004318.GB2185@aditya> Message-ID: <4a10244d.16538c0a.06a6.5982@mx.google.com> On Sat, May 16, 2009 at 08:22:19PM +0000, Saifi Khan wrote: > On Mon, 27 Apr 2009, Aditya Sarawgi wrote: > > > I'm getting Dell Studio 15 and Dell Vostro 1510 (same config) in around the same price. The main > > difference being Studio 15 has a ATI radeon HD 4570 and Vostro 1510 has nvidia 8400 GS. So for which one > > should I go for ? > > How about purchasing the components and assembling > a good system yourself ? > > Let me know if you need help with that. > > > thanks > Saifi. I bought a Dell Vostro 1510 and I'm pretty happy with it, most of the things work out of the box on freebsd. So maybe next time. Cheers, Aditya Sarawgi From mav at FreeBSD.org Sun May 17 14:58:45 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Sun May 17 14:59:01 2009 Subject: CURRENT && HDA Driver Revision: 20090401_0132 && no recording In-Reply-To: <20090517091947.GA2887@current.Sisis.de> References: <1242469381.00112742.1242456003@10.7.7.3> <4A0F31F0.8090601@FreeBSD.org> <20090517091947.GA2887@current.Sisis.de> Message-ID: <4A10261B.5040601@FreeBSD.org> Matthias Apitz wrote: > El d?a Sunday, May 17, 2009 a las 12:36:48AM +0300, Alexander Motin escribi?: >> You have 3 recording sources available via 2 pcm devices. As I can see, >> your built-in mic assigned to pcm1 device. Have you tried to record from >> pcm1? > > It was even more simple. I was only thinking that recording was not > working because I could not hear my own voice while speaking in the > headset (what I can hear for example in the EeePC 900 using snd_hda > too); that's why I did not tried the Echo Service of Skype; later on I > did tried it and it records fine from 'mic': Some codecs (like mine ALC268) just unable to do echo in hardware. For some others, with recording from playback mixer, snd_hda just unable to configure such echo. Last could probably be fixed by adding some more logic to the parser, but I just don't see good reason for this, except probably just singing karaoke, which I don't like. :) -- Alexander Motin From mobile at freebsd.org Mon May 18 01:56:58 2009 From: mobile at freebsd.org (jonnie2) Date: Mon May 18 01:57:05 2009 Subject: An e-card from jonnie2 for you Message-ID: An e-card from jonnie2 for you ========================================= To view the ecard, copy and paste this url into your browser's address bar:: http://www.orni.to/cartes/displayecard.php?data=YTo5OntzOjI6InJuIjtzOjc6Impvbm5pZTIiO3M6Mjoic24iO3M6Nzoiam9ubmllMiI7czoyOiJzZSI7czoxODoibW9iaWxlQGZyZWVic2Qub3JnIjtzOjE6InAiO3M6NTY6Imh0dHA6Ly93d3cub3JuaS50by9jYXJ0ZXMvYWxidW1zL3VzZXJwaWNzLzEwMDAxLzIwMDYuanBnIjtzOjE6ImciO3M6OToiVnRwSmxZRGdNIjtzOjE6Im0iO3M6MTA6ImNvbW1lbnQzLCAiO3M6MzoicGlkIjtpOjE3MTtzOjI6InB0IjtzOjE5OiJIaXJvbmRlbGxlIHJ1c3RpcXVlIjtzOjI6InBjIjtzOjc0OiJIaXJvbmRlbGxlIHJ1c3RpcXVlICg8aT5IaXJ1bmRvIHJ1c3RpY2E8L2k%2BKTxiciAvPg0KKHBob3RvOiBNYXJjIERlbHNhbGxlKSI7fQ%3D%3D VtpJlYDgM comment3, jonnie2 (mobile@freebsd.org) ----------------------------------------- View more pictures !: http://www.orni.to/cartes/ From peter at vk2pj.dyndns.org Tue May 19 02:27:16 2009 From: peter at vk2pj.dyndns.org (Peter Jeremy) Date: Tue May 19 02:27:23 2009 Subject: eeePC - disabling tap In-Reply-To: <4A0EDB58.8050809@langille.org> References: <4A0DE5C1.3070808@langille.org> <44a99a465da3d2724e186d159984e679.squirrel@10.1.1.10> <3a142e750905160502v53c3891bq2fd852c1aafd2f1e@mail.gmail.com> <4A0EDB58.8050809@langille.org> Message-ID: <20090519022709.GA97109@server.vk2pj.dyndns.org> On 2009-May-16 11:27:20 -0400, Dan Langille wrote: >psm0: model IntelliMouse, device ID 3 I have one of those (or actually a Synaptics emulating an IntelliMouse) on a HP nx6125 and the tap 'just works' so I've never looked further. >> Maybe you need to use X11 synaptic driver(guessing). This isn't necessary. I have to run the Acer Aspire One touchpad as a Synaptics mouse because it doesn't emulate anything (other than a dumb mouse). I do this with 'hw.psm.synaptics_support="1"' in my loader.conf and then use moused and xf86-input-mouse - I have full tap and scroll support (though the button handling is somewhat dodgy). There are a pile of hw.psm.synaptics sysctls to control it (though I haven't needed to tweak any). -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090519/e63f69b1/attachment.pgp From debt at officehlp4u.com Wed May 20 15:38:00 2009 From: debt at officehlp4u.com (debt@officehlp4u.com) Date: Wed May 20 15:38:07 2009 Subject: Your Payment Message-ID: <20090520113751.D45343A09923311D@officehlp4u.com> The following not refinance the payments: Tired of being told no by the existing loan to terms that the new government home * H.E.L.P. NOW program * We may be able to refinance your home even if you do not any equity in your home. Rates starting a * We negotiate with your lender o can afford. * Typical results include: Reduced mortgage payment, Two to months without a mortgage payment, re reduced principle balance (loan balance) and fixed rate * We also offer access to our Rea program, Short sale specialist. Dont lose y to H.E.L.P. Now &n Log onto: :DEL] < href="http://www.usaloanmod.com">www. Doesn't matter if your upside checks in most cases. Most of our clie damaged FICO scores. Our negotiation agents can s to have your loan rate or amount or terms modified so you in your home and afford your payments. Log onto: [1]w References 1. ="http://www.usaloanmod.com/" From debt at officehlp4u.com Thu May 21 21:11:59 2009 From: debt at officehlp4u.com (debt@officehlp4u.com) Date: Thu May 21 21:12:05 2009 Subject: Your Payment Message-ID: <20090521171146.75B0E481AC8B30B2@officehlp4u.com> The following not refinance the payments: Tired of being told no by the existing loan to terms that the new government home * H.E.L.P. NOW program * We may be able to refinance your home even if you do not any equity in your home. Rates starting a * We negotiate with your lender o can afford. * Typical results include: Reduced mortgage payment, Two to months without a mortgage payment, re reduced principle balance (loan balance) and fixed rate * We also offer access to our Rea program, Short sale specialist. Dont lose y to H.E.L.P. Now &n Log onto: :DEL] < href="http://www.usaloanmod.com">www. Doesn't matter if your upside checks in most cases. Most of our clie damaged FICO scores. Our negotiation agents can s to have your loan rate or amount or terms modified so you in your home and afford your payments. Log onto: [1]w References 1. ="http://www.usaloanmod.com/" From gabor at FreeBSD.org Sat May 23 14:11:58 2009 From: gabor at FreeBSD.org (Gabor Kovesdan) Date: Sat May 23 14:12:05 2009 Subject: netbooks vs FreeBSD Message-ID: <4A17FFAF.4010400@FreeBSD.org> Hello, I'm about to buy a netbook, which: - is compatible with FreeBSD (wifi is especially important) - has a good battery life (at least 4 hours) - has a normal HDD not an SSD I was told that the new 6 cell Acer Aspire ONEs aren't bad. Could you share your experiences about the following models, please? Or of course, if you have other suggestions, I'm open to them. Acer Aspire one D250-1B Acer Aspire one D150-1B MSI WIND U100-029HU (this one is very tempting because of the 2GB RAM and the 2-year warranty) Thanks in advance, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From wojtek at wojtek.tensor.gdynia.pl Sat May 23 16:09:50 2009 From: wojtek at wojtek.tensor.gdynia.pl (Wojciech Puchar) Date: Sat May 23 16:09:56 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A17FFAF.4010400@FreeBSD.org> References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: > > I'm about to buy a netbook, which: > - is compatible with FreeBSD (wifi is especially important) > - has a good battery life (at least 4 hours) > - has a normal HDD not an SSD point 2 and 3 is somehow incompatible - HDD takes more power. anyway in order of few watts, compared to CPUs taking 20-50W, excluding those really "mobile". so >4 hours on battery&HDD seems possible. From a.j.werven at student.utwente.nl Sat May 23 17:10:54 2009 From: a.j.werven at student.utwente.nl (A.J. "Fonz" van Werven) Date: Sat May 23 17:11:01 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A17FFAF.4010400@FreeBSD.org> Message-ID: <200905231632.n4NGWLOC005409@satellite.xs4all.nl> Gabor Kovesdan wrote: > I'm about to buy a netbook, which: > - is compatible with FreeBSD (wifi is especially important) It would be nice if the builtin card works with FreeBSD but if not, there are USB WiFi adapters that do. > - has a normal HDD not an SSD Speaking of disks, what is the typical HDD size range of netbooks nowadays? Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- Pope Benedict XVI, Southpark season 11 episode 5 From Millenia2000 at hotmail.com Sat May 23 17:43:49 2009 From: Millenia2000 at hotmail.com (Sean Cavanaugh) Date: Sat May 23 17:43:54 2009 Subject: netbooks vs FreeBSD In-Reply-To: References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: -------------------------------------------------- From: "Wojciech Puchar" Sent: Saturday, May 23, 2009 12:09 PM To: "Gabor Kovesdan" Cc: ; Subject: Re: netbooks vs FreeBSD >> >> I'm about to buy a netbook, which: >> - is compatible with FreeBSD (wifi is especially important) >> - has a good battery life (at least 4 hours) >> - has a normal HDD not an SSD > > point 2 and 3 is somehow incompatible - HDD takes more power. anyway in > order of few watts, compared to CPUs taking 20-50W, excluding those really > "mobile". so >4 hours on battery&HDD seems possible. > I respectfully disagree. As much as I hate Apple as a company, I currently have a MacBook Pro that gets over 4 hours of battery life and has a 200+gig HDD in it. From wojtek at wojtek.tensor.gdynia.pl Sat May 23 20:40:44 2009 From: wojtek at wojtek.tensor.gdynia.pl (Wojciech Puchar) Date: Sat May 23 20:40:56 2009 Subject: netbooks vs FreeBSD In-Reply-To: References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: >> >> point 2 and 3 is somehow incompatible - HDD takes more power. anyway in >> order of few watts, compared to CPUs taking 20-50W, excluding those really >> "mobile". so >4 hours on battery&HDD seems possible. >> > > I respectfully disagree. As much as I hate Apple as a company, I currently > have a MacBook Pro that gets over 4 hours of battery life and has a 200+gig > HDD in it. > i wrote "somehow incompatible" :) your macbook pro would run even more hours on the same battery with flash drive. i don't know how much your CPU gets power, and ... how oversized battery it has From gaijin.k at gmail.com Sat May 23 20:58:00 2009 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sat May 23 20:58:06 2009 Subject: netbooks vs FreeBSD In-Reply-To: References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: <1243112254.1200.11.camel@RabbitsDen> On Sat, 2009-05-23 at 13:31 -0400, Sean Cavanaugh wrote: > -------------------------------------------------- > From: "Wojciech Puchar" > Sent: Saturday, May 23, 2009 12:09 PM > To: "Gabor Kovesdan" > Cc: ; > Subject: Re: netbooks vs FreeBSD > > >> > >> I'm about to buy a netbook, which: > >> - is compatible with FreeBSD (wifi is especially important) > >> - has a good battery life (at least 4 hours) > >> - has a normal HDD not an SSD > > > > point 2 and 3 is somehow incompatible - HDD takes more power. anyway in > > order of few watts, compared to CPUs taking 20-50W, excluding those really > > "mobile". so >4 hours on battery&HDD seems possible. > > > > I respectfully disagree. As much as I hate Apple as a company, I currently > have a MacBook Pro that gets over 4 hours of battery life and has a 200+gig > HDD in it. > I did not run FreeBSD on it, so I apologize for slight OT, but my wife's Samsung NC10 (2.8 lbs, 10.2" screen, 160GB 5400RPM HDD) is pushing 6 hours of the battery life with the wireless on and memory upgraded to 2GB. This is under Windows XP HOME ULCPC though. Wireless card (as reported by Windows) is Atheros AR5007EG, so you might need to ask around whether it is supported by ath driver. HTH, -- Alexandre Kovalenko (????????? ?????????) From gabor at FreeBSD.org Sun May 24 13:33:53 2009 From: gabor at FreeBSD.org (Gabor Kovesdan) Date: Sun May 24 13:34:00 2009 Subject: netbooks vs FreeBSD In-Reply-To: References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: <4A194CB7.4080605@FreeBSD.org> Wojciech Puchar escribi?: >> >> I'm about to buy a netbook, which: >> - is compatible with FreeBSD (wifi is especially important) >> - has a good battery life (at least 4 hours) >> - has a normal HDD not an SSD > > point 2 and 3 is somehow incompatible - HDD takes more power. anyway > in order of few watts, compared to CPUs taking 20-50W, excluding those > really "mobile". so >4 hours on battery&HDD seems possible. > Yes, but buying anything is always about compromises. Recent HDD models are pretty good and I don't need the most hi-end model with an extreme battery life, just a reasonable uptime with HDD. I think I'll go for the Acer Aspire ONE. I haven't got comments from these lists about that model in particular but I googled a bit and it seems mostly everything works with it. -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From gabor at FreeBSD.org Sun May 24 13:37:43 2009 From: gabor at FreeBSD.org (Gabor Kovesdan) Date: Sun May 24 13:37:49 2009 Subject: netbooks vs FreeBSD In-Reply-To: <200905231632.n4NGWLOC005409@satellite.xs4all.nl> References: <200905231632.n4NGWLOC005409@satellite.xs4all.nl> Message-ID: <4A194D9F.1020309@FreeBSD.org> A.J. "Fonz" van Werven escribi?: > Gabor Kovesdan wrote: > > >> I'm about to buy a netbook, which: >> - is compatible with FreeBSD (wifi is especially important) >> > > It would be nice if the builtin card works with FreeBSD but if not, there > are USB WiFi adapters that do. > That's what I want to avoid. :) Nowadays, you can buy almost anything as an external USB accessories but what's the point in integrated goodies then? :) > >> - has a normal HDD not an SSD >> > > Speaking of disks, what is the typical HDD size range of netbooks > nowadays? > I've seen model with ~120-160 GB. That's enough for me. I'll buy a netbook mainly because of the good mobility. Browsing, reading mail, coding, ... I think it'll be fine for these requirements. -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From gabor at FreeBSD.org Sun May 24 13:44:02 2009 From: gabor at FreeBSD.org (Gabor Kovesdan) Date: Sun May 24 13:44:13 2009 Subject: netbooks vs FreeBSD In-Reply-To: <1243112254.1200.11.camel@RabbitsDen> References: <4A17FFAF.4010400@FreeBSD.org> <1243112254.1200.11.camel@RabbitsDen> Message-ID: <4A194F19.9070106@FreeBSD.org> Alexandre "Sunny" Kovalenko escribi?: > I did not run FreeBSD on it, so I apologize for slight OT, but my wife's > Samsung NC10 (2.8 lbs, 10.2" screen, 160GB 5400RPM HDD) is pushing 6 > hours of the battery life with the wireless on and memory upgraded to > 2GB. This is under Windows XP HOME ULCPC though. > > Wireless card (as reported by Windows) is Atheros AR5007EG, so you might > need to ask around whether it is supported by ath driver. > Thanks, that Samsung model seems pretty nice, as well, but it's significantly more expensive in Hungary than the Aspire ONE, while the specs are mainly the same. So I think I'll go for the Acer netbook if someone doesn't convince me quickly not to do so... -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From guru at unixarea.de Sun May 24 13:52:33 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sun May 24 13:52:40 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A194F19.9070106@FreeBSD.org> References: <4A17FFAF.4010400@FreeBSD.org> <1243112254.1200.11.camel@RabbitsDen> <4A194F19.9070106@FreeBSD.org> Message-ID: <20090524135229.GA3410@current.Sisis.de> El d?a Sunday, May 24, 2009 a las 03:43:53PM +0200, Gabor Kovesdan escribi?: > Alexandre "Sunny" Kovalenko escribi?: > >I did not run FreeBSD on it, so I apologize for slight OT, but my wife's > >Samsung NC10 (2.8 lbs, 10.2" screen, 160GB 5400RPM HDD) is pushing 6 > >hours of the battery life with the wireless on and memory upgraded to > >2GB. This is under Windows XP HOME ULCPC though. > > > >Wireless card (as reported by Windows) is Atheros AR5007EG, so you might > >need to ask around whether it is supported by ath driver. > > > Thanks, that Samsung model seems pretty nice, as well, but it's > significantly more expensive in Hungary than the Aspire ONE, while the > specs are mainly the same. So I think I'll go for the Acer netbook if > someone doesn't convince me quickly not to do so... I have a real netbook, an EeePC 900 with 20 GByte SSD, Wifi, 1024x600 9" display and an attached USB Huawei E220 dongel for UMTS. I have installed 8-CURRENT and all works as it should, only the inbuild cam is not supported, but I don't neet this at the moment (maybe later when Skype for FreeBSD can do video as well). matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From meta at club.kyutech.ac.jp Sun May 24 17:27:33 2009 From: meta at club.kyutech.ac.jp (Koichiro IWAO) Date: Sun May 24 17:28:06 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A17FFAF.4010400@FreeBSD.org> References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: <4A197E77.2060500@club.kyutech.ac.jp> Hi. Gabor Kovesdan ????????: > Hello, > > I'm about to buy a netbook, which: > - is compatible with FreeBSD (wifi is especially important) > - has a good battery life (at least 4 hours) > - has a normal HDD not an SSD I don't know about that you are going to buy, but I have Dell Inspiron mini 12. One of the big problem with FreeBSD is the video Driver. Most of netbooks have Intel Atom Z series CPU. Atom Z series have integrated chipset and video chip. The integrated video chip Intel GMA 500 is not a original Intel product. So X11 does not work with Intel driver and the driver is still unavailable. VESA is the only available driver. If you want use X11, do not forget to choose Atom N series. -- Iwao, Koichiro From gabor at FreeBSD.org Sun May 24 18:09:47 2009 From: gabor at FreeBSD.org (Gabor Kovesdan) Date: Sun May 24 18:09:59 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A197E77.2060500@club.kyutech.ac.jp> References: <4A17FFAF.4010400@FreeBSD.org> <4A197E77.2060500@club.kyutech.ac.jp> Message-ID: <4A198D5F.1090405@FreeBSD.org> Koichiro IWAO escribi?: > The integrated video chip Intel GMA 500 is not a original Intel product. > So X11 does not work with Intel driver and the driver is still > unavailable. VESA is the only available driver. > > If you want use X11, do not forget to choose Atom N series. Uh, thanks a lot, I almost chose the 751h model, but now I decided to take the 531. It comes with Intel 945GM. -- Gabor Kovesdan FreeBSD Volunteer EMAIL: gabor@FreeBSD.org .:|:. gabor@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org From rnoland at FreeBSD.org Mon May 25 14:30:07 2009 From: rnoland at FreeBSD.org (Robert Noland) Date: Mon May 25 14:30:20 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A198D5F.1090405@FreeBSD.org> References: <4A17FFAF.4010400@FreeBSD.org> <4A197E77.2060500@club.kyutech.ac.jp> <4A198D5F.1090405@FreeBSD.org> Message-ID: <1243261740.1787.1033.camel@balrog.2hip.net> On Sun, 2009-05-24 at 20:09 +0200, Gabor Kovesdan wrote: > Koichiro IWAO escribi?: > > The integrated video chip Intel GMA 500 is not a original Intel product. > > So X11 does not work with Intel driver and the driver is still > > unavailable. VESA is the only available driver. Does anyone have the pci ids for this? I have some patches around here for an "IGD" device that I think is a G41 but afaik was un-released at the time that I created that patch. robert. > > If you want use X11, do not forget to choose Atom N series. > Uh, thanks a lot, I almost chose the 751h model, but now I decided to > take the 531. It comes with Intel 945GM. -- Robert Noland FreeBSD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090525/a9d9c5f0/attachment.pgp From parv at pair.com Mon May 25 22:58:41 2009 From: parv at pair.com (parv@pair.com) Date: Mon May 25 22:58:53 2009 Subject: netbooks vs FreeBSD In-Reply-To: <20090524135229.GA3410@current.Sisis.de> References: <4A17FFAF.4010400@FreeBSD.org> <1243112254.1200.11.camel@RabbitsDen> <4A194F19.9070106@FreeBSD.org> <20090524135229.GA3410@current.Sisis.de> Message-ID: <20090525222212.GA1445@holstein.holy.cow> in message <20090524135229.GA3410@current.Sisis.de>, wrote Matthias Apitz thusly... > > > Alexandre "Sunny" Kovalenko escribi?: > > >I did not run FreeBSD on it, so I apologize for slight OT, but > > >my wife's Samsung NC10 (2.8 lbs, 10.2" screen, 160GB 5400RPM > > >HDD) is pushing 6 hours of the battery life with the wireless > > >on and memory upgraded to 2GB. This is under Windows XP HOME > > >ULCPC though. ... > I have a real netbook, an EeePC 900 with 20 GByte SSD, Wifi, > 1024x600 9" display and an attached USB Huawei E220 dongel for > UMTS. I have installed 8-CURRENT and all works as it should, only > the inbuild cam is not supported, but I don't neet this at the > moment (maybe later when Skype for FreeBSD can do video as well). Matthias, What kind of battery life do you get (with and without WIFI use)? - Parv -- From wojtek at wojtek.tensor.gdynia.pl Tue May 26 01:09:52 2009 From: wojtek at wojtek.tensor.gdynia.pl (Wojciech Puchar) Date: Tue May 26 01:09:58 2009 Subject: netbooks vs FreeBSD In-Reply-To: <20090525222212.GA1445@holstein.holy.cow> References: <4A17FFAF.4010400@FreeBSD.org> <1243112254.1200.11.camel@RabbitsDen> <4A194F19.9070106@FreeBSD.org> <20090524135229.GA3410@current.Sisis.de> <20090525222212.GA1445@holstein.holy.cow> Message-ID: >> 1024x600 9" display and an attached USB Huawei E220 dongel for >> UMTS. I have installed 8-CURRENT and all works as it should, only >> the inbuild cam is not supported, but I don't neet this at the >> moment (maybe later when Skype for FreeBSD can do video as well). > > Matthias, > > What kind of battery life do you get (with and without WIFI use)? > and with/without Huawei E220. it's realy heavy battery drainer, takes much more than WiFi - i have this UMTS interface. From newsletter at ownersdirect.co.uk Tue May 26 09:38:52 2009 From: newsletter at ownersdirect.co.uk (Owners Direct) Date: Tue May 26 09:38:59 2009 Subject: Find the perfect priced accommodation for your next holiday! Message-ID: <{4B0942FA-8102-4139-8B90-4020F1B07BC3}odhr_bounce@clients.intrasight.net> ---------------------------------------------------------------- Over 31,000 holiday rentals worldwide direct from private owners ---------------------------------------------------------------- Dear Holidaymaker, With over 31,000 properties on Owners Direct, you're spoilt for choice! Whatever your requirements, we are confident that you will find the perfect accommodation for your next holiday. For great prices, browse the special offer listings or for more refined searching use our advanced search facility. http://www.ownersdirect.co.uk http://www.ownersdirect.co.uk/search-special-offer-accommodation.asp ----------------------------------------------------------- Discover Greece ----------------------------------------------------------- Whatever you're looking for in you're next holiday - you're sure to find something to suit you in Greece or one of its beautiful Islands. Corfu offers a buzzing nightlife and activities, Santorini is famous for its fascinating landscapes or if you are looking for historical and cultural diversity visit the island of Chania. All of the Greek Islands share the same fantastic summer sunshine and friendly locals. If you check out the special offer listing you'll find some great prices too! http://www.ownersdirect.co.uk/Greece.htm http://www.ownersdirect.co.uk/search-special-offer-accommodation.asp http://www.ownersdirect.co.uk/corfu.htm http://www.ownersdirect.co.uk/santorini.htm http://www.ownersdirect.co.uk/Crete-Chania.htm http://www.ownersdirect.co.uk/kefalonia.htm http://www.ownersdirect.co.uk/rhodes.htm http://www.ownersdirect.co.uk/zakynthos.htm http://www.ownersdirect.co.uk/lefkas.htm http://www.ownersdirect.co.uk/alonnissos.htm http://www.ownersdirect.co.uk/skiathos.htm --------------------------------------------------------------------- Spend Less Long Haul --------------------------------------------------------------------- If you have always wanted to travel further afield but been worried about the cost, you may find it is cheaper than you expected. You will you find some great prices for self catering accommodation in comparison to hotel stays and the cost of living can be significanlty cheaper than destinations closer to home - a 3 course meal for 2 people in Thailand being up to 40% cheaper than in many countries in Europe. See how far your budget can take you! http://www.ownersdirect.co.uk/Thailand.htm http://www.ownersdirect.co.uk/South-Africa.htm http://www.ownersdirect.co.uk/Australia.htm http://www.ownersdirect.co.uk/Kenya.htm http://www.ownersdirect.co.uk/Morocco.htm http://www.ownersdirect.co.uk/India.htm http://www.ownersdirect.co.uk/USA.htm ---------------------------------------------------------------------- Brilliant Beach Holidays ---------------------------------------------------------------------- For many, spending time on a beach is the most important part of a holiday and on Owners Direct we have thousands of properties with easy access to some amazing beaches. Check out properties in Ibiza for miles of golden sand or sea front villas in Cyprus where the clear waters are ideal for swimming and snorkelling. If you want to escape the crowds, beaches in Northern Spain along the rugged coastline are undeveloped and perfect for relaxation. http://www.ownersdirect.co.uk/ http://www.ownersdirect.co.uk/Cyprus.htm http://www.ownersdirect.co.uk/galicia.htm http://www.ownersdirect.co.uk/Croatia.htm http://www.ownersdirect.co.uk/Portugal.htm http://www.ownersdirect.co.uk/Turkey.htm http://www.ownersdirect.co.uk/Canary-Islands.htm http://www.ownersdirect.co.uk/France.htm http://www.ownersdirect.co.uk/Bulgaria.htm ---------------------------------------------------------------------- Rent with Confidence ---------------------------------------------------------------------- Because we understand how important it is for you to feel confident in booking the properties on our website, we have introduced a holiday rental guarantee scheme to protect travellers against fraud. Now you can rent your holiday home with confidence. http://guaranteeuk.homeaway.com/ ---------------------------------------------------------------------- Do you own a holiday home? ---------------------------------------------------------------------- We specialise in advertising privately owned accommodation so why not try advertising your property on Owners Direct? Click here to find out more. http://www.ownersdirect.co.uk/advertise.htm Angela Southall Marketing Manager Owners Direct Holiday Rentals Ltd Tel: + 44 (0)1372 229330 Fax: + 44 (0)1372 229339 Email: support@ownersdirect.co.uk ---------------------------------------------------- Owners Direct Holiday Rentals Ltd 1997 - 2009 Please do not reply to this email. It has been sent from an email address that does not accept incoming emails. This e-mail is never sent unsolicited. This is an Owners Direct mailing. You are currently subscribed as: mobile@freebsd.org If you no longer wish to receive our newsletters then please click here : http://www.ownersdirect.co.uk/unsubscribe.asp?cid=E_may27%20renters_NL_O_20090527_Unsubscribe_Text_LOTH_ From vova at fbsd.ru Tue May 26 14:27:45 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue May 26 14:27:52 2009 Subject: Any success with Lenovo T60 Message-ID: <1243346852.2384.62.camel@localhost> Hi Does anybody managed to make FreeBSD successfully suspend and resume on Lenovo T60 ? FreeBSD 8.0-CURRENT #0: Fri May 22 15:30:36 MSD 2009 root@vbook:/usr/obj/usr/src/sys/VBOOK Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2097184768 (2000 MB) ACPI APIC Table: ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or length: 0 102C/0 [20070320] ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard netsmb_dev: loaded kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7ff00000 (3) failed I've tried but it does not resumes after sleep, so looking for hints. -- Vladimir B. Grebenschikov vova@fbsd.ru From chuckop at gmail.com Tue May 26 21:00:21 2009 From: chuckop at gmail.com (Charles Oppermann) Date: Tue May 26 21:00:33 2009 Subject: Any success with Lenovo T60 In-Reply-To: <1243346852.2384.62.camel@localhost> References: <1243346852.2384.62.camel@localhost> Message-ID: <004601c9de41$81107630$83316290$@com> > Does anybody managed to make FreeBSD successfully suspend and resume on > Lenovo T60 ? Funny, because I was about to ask the same question regarding the T61p. I have heard that SMP prevents suspending entirely, but turning off the second CPU via BIOS doesn't help. I have been using acpiconf -s3 to test. Each time I get a console message saying that suspend event failed. Never does it suspend, nor does it seem to bother the current state. I can continue working normally. > ACPI APIC Table: > ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or > length: 0 102C/0 [20070320] > ioapic0: Changing APIC ID to 1 > ioapic0 irqs 0-23 on motherboard > netsmb_dev: loaded > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: [ITHREAD] > acpi_ec0: port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 7ff00000 (3) failed I get the same ACPI warnings and "failed" as you. My acpi0 has though. I'd be happy to provide more information or do some spelunking if need be. From peterjeremy at optushome.com.au Tue May 26 21:13:06 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Tue May 26 21:13:13 2009 Subject: netbooks vs FreeBSD In-Reply-To: <4A194CB7.4080605@FreeBSD.org> References: <4A17FFAF.4010400@FreeBSD.org> <4A194CB7.4080605@FreeBSD.org> Message-ID: <20090526211300.GA13700@server.vk2pj.dyndns.org> On 2009-May-24 15:33:43 +0200, Gabor Kovesdan wrote: >Acer Aspire ONE. I haven't got comments from these lists about that >model in particular but I googled a bit and it seems mostly everything >works with it. I have the SSD version and everything except the webcam and suspend/ resume works out of the box. With WiFi and camera turned off, I can get over 3 hrs on the std battery doing things like locally reading mail. I have a USB 3G dongle and it's quite power-hungry (1/4 to 1/3 of total power consumption). -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090526/6cd6a679/attachment.pgp From fbsdlists at honeyguide.net Wed May 27 08:02:48 2009 From: fbsdlists at honeyguide.net (Stephan Lichtenauer) Date: Wed May 27 08:03:00 2009 Subject: netbooks vs FreeBSD In-Reply-To: <20090526211300.GA13700@server.vk2pj.dyndns.org> References: <4A17FFAF.4010400@FreeBSD.org> <4A194CB7.4080605@FreeBSD.org> <20090526211300.GA13700@server.vk2pj.dyndns.org> Message-ID: <1C1EA0CA-FC01-4B68-A94F-198376772C80@honeyguide.net> Peter, Am 26.05.2009 um 23:13 schrieb Peter Jeremy: > On 2009-May-24 15:33:43 +0200, Gabor Kovesdan > wrote: >> Acer Aspire ONE. I haven't got comments from these lists about that >> model in particular but I googled a bit and it seems mostly >> everything >> works with it. > > I have the SSD version and everything except the webcam and suspend/ > resume works out of the box. What FreeBSD version are you using? Best regards Stephan From utisoft at googlemail.com Wed May 27 13:58:22 2009 From: utisoft at googlemail.com (Chris Rees) Date: Wed May 27 13:58:27 2009 Subject: netbooks vs FreeBSD In-Reply-To: References: <4A17FFAF.4010400@FreeBSD.org> Message-ID: 2009/5/23 Wojciech Puchar : >> >> I'm about to buy a netbook, which: >> - is compatible with FreeBSD (wifi is especially important) >> - has a good battery life (at least 4 hours) >> - has a normal HDD not an SSD > > point 2 and 3 is somehow incompatible - HDD takes more power. anyway in > order of few watts, compared to CPUs taking 20-50W, excluding those really > "mobile". so >4 hours on battery&HDD seems possible. > http://www.google.com/search?client=safari&rls=en&q=SSD+versus+hard+drive+power&ie=UTF-8&oe=UTF-8 Will you PLEASE start checking what you say before posting! Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? From peterjeremy at optushome.com.au Wed May 27 18:50:52 2009 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Wed May 27 18:50:59 2009 Subject: netbooks vs FreeBSD In-Reply-To: <1C1EA0CA-FC01-4B68-A94F-198376772C80@honeyguide.net> References: <4A17FFAF.4010400@FreeBSD.org> <4A194CB7.4080605@FreeBSD.org> <20090526211300.GA13700@server.vk2pj.dyndns.org> <1C1EA0CA-FC01-4B68-A94F-198376772C80@honeyguide.net> Message-ID: <20090527185046.GA1331@server.vk2pj.dyndns.org> On 2009-May-27 09:47:24 +0200, Stephan Lichtenauer wrote: >>> Acer Aspire ONE. I haven't got comments from these lists about that >> I have the SSD version and everything except the webcam and suspend/ >> resume works out of the box. > >What FreeBSD version are you using? FreeBSD 8-current. -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090527/39d8e203/attachment.pgp From taku at tackymt.homeip.net Thu May 28 09:45:56 2009 From: taku at tackymt.homeip.net (YAMAMOTO, Taku) Date: Thu May 28 09:46:03 2009 Subject: Any success with Lenovo T60 In-Reply-To: <1243346852.2384.62.camel@localhost> References: <1243346852.2384.62.camel@localhost> Message-ID: <20090528184537.b2ac4798.taku@tackymt.homeip.net> Hi Vladimir, I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 which can successfully suspend and resume, though things may be a bit different from your case. There were a couple of pitfalls which I ran into: 0. Pristine kernels for i386 SMP don't support the resume yet. We can either use amd64 ones, stick on i386 UP kernels or apply unofficial patch floating around. 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify!) Disabling it ends up with hanging machine on resume. 2. Disable the USB while suspending; otherwise NMI parity error occurs on resume. (usb2 stack only; the old USB stack didn't have this problem) In rc.suspend (the magic to turn the root hubs off): usbconfig -a 1 set_config 255 In rc.resume (the magic to turn the root hubs on again): usbconfig -a 1 set_config 0 Cheers, -- -|-__ YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - -------------- next part -------------- Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #181: Thu May 7 08:46:45 JST 2009 yamamoto@biotite:/home/yamamoto/work/build/biotite/usr/src/sys/BIOTITE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (1995.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant real memory = 1073741824 (1024 MB) avail memory = 1032323072 (984 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or length: 0 102C/0 [20070320] ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard no match for ZwOpenKey no match for IoOpenDeviceRegistryKey no match for ZwCreateKey no match for ZwDeleteKey acpi0: on motherboard acpi0: [ITHREAD] acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3ff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 1100 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x1800-0x1807 mem 0xee100000-0xee17ffff,0xd0000000-0xdfffffff,0xee200000-0xee23ffff irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xd0000000 256MB info: [drm] Initialized i915 1.6.0 20080730 vgapci1: mem 0xee180000-0xee1fffff at device 2.1 on pci0 hdac0: mem 0xee240000-0xee243fff irq 17 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090401_0132 hdac0: [ITHREAD] pcib1: irq 20 at device 28.0 on pci0 pci2: on pcib1 em0: port 0x2000-0x201f mem 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:16:d3:2f:f4:65 pcib2: irq 21 at device 28.1 on pci0 pci3: on pcib2 ndis0: <11a/b/g/n Wireless LAN Mini-PCI Express Adapter> mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3 ndis0: [ITHREAD] ndis0: NDIS API version: 5.1 pcib3: irq 22 at device 28.2 on pci0 pci4: on pcib3 pcib4: irq 23 at device 28.3 on pci0 pci12: on pcib4 uhci0: port 0x1820-0x183f irq 16 at device 29.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0x1840-0x185f irq 17 at device 29.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0x1860-0x187f irq 18 at device 29.2 on pci0 uhci2: [ITHREAD] usbus2: on uhci2 uhci3: port 0x1880-0x189f irq 19 at device 29.3 on pci0 uhci3: [ITHREAD] usbus3: on uhci3 ehci0: mem 0xee444000-0xee4443ff irq 19 at device 29.7 on pci0 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: on ehci0 pcib5: at device 30.0 on pci0 pci21: on pcib5 cbb0: mem 0xe4300000-0xe4300fff irq 16 at device 0.0 on pci21 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [FILTER] pci21: at device 0.1 (no driver attached) sdhci0: mem 0xe4301800-0xe43018ff irq 18 at device 0.2 on pci21 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] atapci1: port 0x18d0-0x18d7,0x18c4-0x18c7,0x18c8-0x18cf,0x18c0-0x18c3,0x18b0-0x18bf mem 0xee444400-0xee4447ff irq 16 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI Version 01.10 controller with 4 ports PM not supported ata2: on atapci1 ata2: [ITHREAD] ichsmb0: port 0x18e0-0x18ff irq 23 at device 31.3 on pci0 ichsmb0: [ITHREAD] smbus0: on ichsmb0 smb0: on smbus0 acpi_dock0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 battery0: on acpi0 acpi_acad0: on acpi0 acpi_ibm0: on acpi0 cpu0: on acpi0 coretemp0: on cpu0 est0: on cpu0 cpu1: on acpi0 coretemp1: on cpu1 est1: on cpu1 pmtimer0 on isa0 orm0: at iomem 0xcf000-0xcffff,0xd0000-0xd0fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid ORM0000 on isa0 sc0: on isa0 sc0: VGA <12 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0 at vga0 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ad0: 114473MB at ata2-master SATA150 hdac0: HDA Codec #0: Analog Devices AD1981HD hdac0: HDA Codec #1: Conexant (Unknown) pcm0: at cad 0 nid 1 on hdac0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 SMP: AP CPU #1 Launched! Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Trying to mount root from ufs:/dev/ad0s1a ugen3.2: at usbus3 WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD. From takawata at init-main.com Thu May 28 09:56:47 2009 From: takawata at init-main.com (Takanori Watanabe) Date: Thu May 28 09:56:59 2009 Subject: Any success with Lenovo T60 In-Reply-To: Your message of "Thu, 28 May 2009 18:45:37 JST." <20090528184537.b2ac4798.taku@tackymt.homeip.net> Message-ID: <200905280952.n4S9q8bS065093@sana.init-main.com> In message <20090528184537.b2ac4798.taku@tackymt.homeip.net>, "YAMAMOTO, Taku" wrote: >Hi Vladimir, > >I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 >which can successfully suspend and resume, though things may be a bit >different from your case. > >There were a couple of pitfalls which I ran into: > > 0. Pristine kernels for i386 SMP don't support the resume yet. > We can either use amd64 ones, stick on i386 UP kernels or apply > unofficial patch floating around. > > 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify!) > Disabling it ends up with hanging machine on resume. > > 2. Disable the USB while suspending; otherwise NMI parity error occurs > on resume. (usb2 stack only; the old USB stack didn't have this problem) > In rc.suspend (the magic to turn the root hubs off): > usbconfig -a 1 set_config 255 > In rc.resume (the magic to turn the root hubs on again): > usbconfig -a 1 set_config 0 > Is the SMP/i386 patch applied cleanly? Lazy author does not tried that since then. From taku at tackymt.homeip.net Thu May 28 10:13:17 2009 From: taku at tackymt.homeip.net (YAMAMOTO, Taku) Date: Thu May 28 10:13:26 2009 Subject: Any success with Lenovo T60 In-Reply-To: <200905280952.n4S9q8bS065093@sana.init-main.com> References: <20090528184537.b2ac4798.taku@tackymt.homeip.net> <200905280952.n4S9q8bS065093@sana.init-main.com> Message-ID: <20090528191311.b68ab3b7.taku@tackymt.homeip.net> On Thu, 28 May 2009 18:52:08 +0900 Takanori Watanabe wrote: > In message <20090528184537.b2ac4798.taku@tackymt.homeip.net>, "YAMAMOTO, Taku" > wrote: > >Hi Vladimir, > > > >I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 > >which can successfully suspend and resume, though things may be a bit > >different from your case. > > > >There were a couple of pitfalls which I ran into: > > > > 0. Pristine kernels for i386 SMP don't support the resume yet. > > We can either use amd64 ones, stick on i386 UP kernels or apply > > unofficial patch floating around. > > > > 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify!) > > Disabling it ends up with hanging machine on resume. > > > > 2. Disable the USB while suspending; otherwise NMI parity error occurs > > on resume. (usb2 stack only; the old USB stack didn't have this problem) > > In rc.suspend (the magic to turn the root hubs off): > > usbconfig -a 1 set_config 255 > > In rc.resume (the magic to turn the root hubs on again): > > usbconfig -a 1 set_config 0 > > > > Is the SMP/i386 patch applied cleanly? > Lazy author does not tried that since then. No, it requires slight modifications to apply, but that's it. Would it be worth to have it available somewhere? -- -|-__ YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - From takawata at init-main.com Thu May 28 10:27:18 2009 From: takawata at init-main.com (Takanori Watanabe) Date: Thu May 28 10:27:30 2009 Subject: Any success with Lenovo T60 In-Reply-To: Your message of "Thu, 28 May 2009 19:13:11 JST." <20090528191311.b68ab3b7.taku@tackymt.homeip.net> Message-ID: <200905281022.n4SAMdxr065296@sana.init-main.com> In message <20090528191311.b68ab3b7.taku@tackymt.homeip.net>, "YAMAMOTO, Taku" wrote: >On Thu, 28 May 2009 18:52:08 +0900 >Takanori Watanabe wrote: > >> In message <20090528184537.b2ac4798.taku@tackymt.homeip.net>, "YAMAMOTO, Tak >u" >> wrote: >> >Hi Vladimir, >> > >> >I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 >> >which can successfully suspend and resume, though things may be a bit >> >different from your case. >> > >> >There were a couple of pitfalls which I ran into: >> > >> > 0. Pristine kernels for i386 SMP don't support the resume yet. >> > We can either use amd64 ones, stick on i386 UP kernels or apply >> > unofficial patch floating around. >> > >> > 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify! >) >> > Disabling it ends up with hanging machine on resume. >> > >> > 2. Disable the USB while suspending; otherwise NMI parity error occurs >> > on resume. (usb2 stack only; the old USB stack didn't have this problem >) >> > In rc.suspend (the magic to turn the root hubs off): >> > usbconfig -a 1 set_config 255 >> > In rc.resume (the magic to turn the root hubs on again): >> > usbconfig -a 1 set_config 0 >> > >> >> Is the SMP/i386 patch applied cleanly? >> Lazy author does not tried that since then. > >No, it requires slight modifications to apply, but that's it. >Would it be worth to have it available somewhere? Yes, please. I want to review it. From taku at tackymt.homeip.net Thu May 28 11:18:53 2009 From: taku at tackymt.homeip.net (YAMAMOTO, Taku) Date: Thu May 28 11:19:00 2009 Subject: Any success with Lenovo T60 In-Reply-To: <200905281022.n4SAMdxr065296@sana.init-main.com> References: <20090528191311.b68ab3b7.taku@tackymt.homeip.net> <200905281022.n4SAMdxr065296@sana.init-main.com> Message-ID: <20090528201844.7df2e164.taku@tackymt.homeip.net> I'll attach the patch in a Triaez fashion :) though I don't think this is the way to go. # We need to implement suspend_cpus() for i386 and utilize it. On Thu, 28 May 2009 19:22:39 +0900 Takanori Watanabe wrote: > In message <20090528191311.b68ab3b7.taku@tackymt.homeip.net>, "YAMAMOTO, Taku" > wrote: > >On Thu, 28 May 2009 18:52:08 +0900 > >Takanori Watanabe wrote: > > > >> In message <20090528184537.b2ac4798.taku@tackymt.homeip.net>, "YAMAMOTO, Tak > >u" > >> wrote: > >> >Hi Vladimir, > >> > > >> >I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 > >> >which can successfully suspend and resume, though things may be a bit > >> >different from your case. > >> > > >> >There were a couple of pitfalls which I ran into: > >> > > >> > 0. Pristine kernels for i386 SMP don't support the resume yet. > >> > We can either use amd64 ones, stick on i386 UP kernels or apply > >> > unofficial patch floating around. > >> > > >> > 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify! > >) > >> > Disabling it ends up with hanging machine on resume. > >> > > >> > 2. Disable the USB while suspending; otherwise NMI parity error occurs > >> > on resume. (usb2 stack only; the old USB stack didn't have this problem > >) > >> > In rc.suspend (the magic to turn the root hubs off): > >> > usbconfig -a 1 set_config 255 > >> > In rc.resume (the magic to turn the root hubs on again): > >> > usbconfig -a 1 set_config 0 > >> > > >> > >> Is the SMP/i386 patch applied cleanly? > >> Lazy author does not tried that since then. > > > >No, it requires slight modifications to apply, but that's it. > >Would it be worth to have it available somewhere? > > Yes, please. I want to review it. -- -|-__ YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - -------------- next part -------------- A non-text attachment was scrubbed... Name: takawata-mpresume-r189903.patch Type: text/x-diff Size: 8874 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090528/54b9cc1d/takawata-mpresume-r189903.bin From debt at officehlp4u.com Thu May 28 22:03:46 2009 From: debt at officehlp4u.com (debt@officehlp4u.com) Date: Thu May 28 22:03:53 2009 Subject: Your Payment Message-ID: <20090528180334.494C891441F59B67@officehlp4u.com> The following not refinance the payments: Tired of being told no by the existing loan to terms that the new government home * H.E.L.P. NOW program * We may be able to refinance your home even if you do not any equity in your home. Rates starting a * We negotiate with your lender o can afford. * Typical results include: Reduced mortgage payment, Two to months without a mortgage payment, re reduced principle balance (loan balance) and fixed rate * We also offer access to our Rea program, Short sale specialist. Dont lose y to H.E.L.P. Now &n Log onto: :DEL] < href="http://www.usaloanmod.com">www. Doesn't matter if your upside checks in most cases. Most of our clie damaged FICO scores. Our negotiation agents can s to have your loan rate or amount or terms modified so you in your home and afford your payments. Log onto: [1]w References 1. ="http://www.usaloanmod.com/" From oberman at es.net Fri May 29 03:42:06 2009 From: oberman at es.net (Kevin Oberman) Date: Fri May 29 03:42:17 2009 Subject: Any success with Lenovo T60 In-Reply-To: Your message of "Thu, 28 May 2009 18:45:37 +0900." <20090528184537.b2ac4798.taku@tackymt.homeip.net> Message-ID: <20090529034156.BBDA51CC09@ptavv.es.net> > Date: Thu, 28 May 2009 18:45:37 +0900 > From: "YAMAMOTO, Taku" > Sender: owner-freebsd-mobile@freebsd.org > > Hi Vladimir, > > I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 > which can successfully suspend and resume, though things may be a bit > different from your case. > > There were a couple of pitfalls which I ran into: > > 0. Pristine kernels for i386 SMP don't support the resume yet. > We can either use amd64 ones, stick on i386 UP kernels or apply > unofficial patch floating around. > > 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify!) > Disabling it ends up with hanging machine on resume. Do you mean in BIOS? I've been fighting with resume issues on my T43 and I suspect that this may be at least a part of the problem. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From Juergen.Dankoweit at t-online.de Fri May 29 05:23:31 2009 From: Juergen.Dankoweit at t-online.de (=?ISO-8859-15?Q?J=FCrgen_Dankoweit?=) Date: Fri May 29 05:23:43 2009 Subject: Any success with Lenovo T60 In-Reply-To: <20090529034156.BBDA51CC09@ptavv.es.net> References: <20090529034156.BBDA51CC09@ptavv.es.net> Message-ID: <4A1F6DAF.1080108@FreeBSD-Onkel.de> Hello Kevin, Kevin Oberman schrieb: >> Date: Thu, 28 May 2009 18:45:37 +0900 >> From: "YAMAMOTO, Taku" >> Sender: owner-freebsd-mobile@freebsd.org >> >> Hi Vladimir, >> >> I have an X60 running 8.0-current/i386 as of Apr. 29, 2009 >> which can successfully suspend and resume, though things may be a bit >> different from your case. >> >> There were a couple of pitfalls which I ran into: >> >> 0. Pristine kernels for i386 SMP don't support the resume yet. >> We can either use amd64 ones, stick on i386 UP kernels or apply >> unofficial patch floating around. >> >> 1. DO NOT DISABLE the built-in modem! (It took almost 2 weeks to identify!) >> Disabling it ends up with hanging machine on resume. > > Do you mean in BIOS? > > I've been fighting with resume issues on my T43 and I suspect that this > may be at least a part of the problem. > > Thanks! with my T43 I had similar problems. After disabling APIC (not ACPI!) everything works perfect. Also look here: http://www.thinkwiki.org/wiki/Installing_FreeBSD_7_on_a_ThinkPad_T43 Best regards Juergen From guru at unixarea.de Fri May 29 10:48:06 2009 From: guru at unixarea.de (Matthias Apitz) Date: Fri May 29 10:48:13 2009 Subject: laptop Dell M4400 with -CURRENT? In-Reply-To: <49F85387.8000201@bahnhofbredband.se> References: <20090428083627.GA3621@rebelion.Sisis.de> <49F715F6.8020603@freebsd.org> <49F71E49.7090001@aol.com> <20090429111016.GA7546@rebelion.Sisis.de> <49F85387.8000201@bahnhofbredband.se> Message-ID: <20090529104758.GA1854@current.Sisis.de> El d?a Wednesday, April 29, 2009 a las 03:17:59PM +0200, Carl Johan Gustavsson escribi?: > Matthias Apitz wrote: > > > >Yes, the configurator at dell.com let me select between: > > > >--EMEA Intel Pro Wireless WI-FI 5100 (802.11a/g/ Draft-n 1X2) MiniCard for > >Centrino 2 Label > >--EMEA Intel Pro Wireless 5300 (802.11a/g/ Draft-n 3x3) MiniCard for > >Centrino 2 Label > >--EMEA Dell Wireless 1510 (802.11a/b/g/n 2X3) MiniCard for Core 2 Duo Label > > > >are the two Intel cards supported? and by which module? thx > > > > matthias > The two Intel cards are not supported at the moment but I have seen > that there are some work in progress on them (OpenBSD have a driver for > them). The Dell branded card has a Broadcom chipset it seems, > (bcm94312hmg) and thats not supported either AFAIK. > > One option is to order it without WiFi and put in some Atheros card > yourself (which I did). > > Carl Just to close this thread: I've ordered an Atheros Wifi smallPCI card as well, inserted it into the laptop into the empty WWAN slot (btw: Dell's HTML and picture documentation about how to open the box and do replacements is *very* good); the biggest issue was to connect the two micro antenna plugs onto the card; but after this all is fine now: $ dmesg | fgrep ath ath0: mem 0xf1ff0000-0xf1ffffff irq 16 at device 0.0 on pci11 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 $ ifconfig ath0 ath0: flags=8843 metric 0 mtu 2290 ether 00:22:43:29:22:cd media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated $ ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:22:43:29:22:cd inet 10.0.1.222 netmask 0xffffff00 broadcast 10.0.1.255 media: IEEE 802.11 Wireless Ethernet OFDM/18Mbps mode 11g status: associated ssid XXXXXXXXXX channel 7 (2442 Mhz 11g) bssid 00:04:e2:a1:76:0b regdomain 96 indoor ecm authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL Carl, thanks again for your hint. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From guru at unixarea.de Fri May 29 13:49:59 2009 From: guru at unixarea.de (Matthias Apitz) Date: Fri May 29 13:50:11 2009 Subject: CURRENT && HDA Driver Revision: 20090401_0132 && no recording In-Reply-To: <4A0F31F0.8090601@FreeBSD.org> References: <1242469381.00112742.1242456003@10.7.7.3> <4A0F31F0.8090601@FreeBSD.org> Message-ID: <20090529134950.GA3146@current.Sisis.de> El d?a Sunday, May 17, 2009 a las 12:36:48AM +0300, Alexander Motin escribi?: > Matthias Apitz wrote: > >I can't get to work recording in environment -CURRENT && HDA Driver > >Revision: 20090401_0132 > > > >the sound output is fine in KDE, but as well the KDE mixer does > >not control it; only with mixer(1) command I can change the volume for > >example; I've already tried all values for setting > > > >$ mixer =rec rdev > > > >but nothing helps switching on the micro. The man page of snd_hda(4) > >explains a lot of device.hints(5) options, but understanding all this is > >out of my control; I'm attaching a 'dmesg | fgrep hdac'. > > > >Any idea how to get recording switched on? I need this for business for > >Skype... This is the last blocking point to switch over to my new Dell > >M4400 > > You have 3 recording sources available via 2 pcm devices. As I can see, > your built-in mic assigned to pcm1 device. Have you tried to record from > pcm1? > > PS: `dmesg | fgrep pcm` is also interesting. As said already, recording from the mic jack for the headset works fine (even without local echo to headset or loudspeaker). How could I record from the built-in mic, i.e. without the headset plug'ed in into the mic jack? I'm attaching 'dmesg | fgrep pcm' as well. Thanks for a hint. matthias pcm0: at cad 0 nid 1 on hdac0 pcm1: at cad 0 nid 1 on hdac0 pcm2: at cad 0 nid 1 on hdac0 -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From mav at FreeBSD.org Fri May 29 13:55:39 2009 From: mav at FreeBSD.org (Alexander Motin) Date: Fri May 29 13:55:55 2009 Subject: CURRENT && HDA Driver Revision: 20090401_0132 && no recording In-Reply-To: <20090529134950.GA3146@current.Sisis.de> References: <1242469381.00112742.1242456003@10.7.7.3> <4A0F31F0.8090601@FreeBSD.org> <20090529134950.GA3146@current.Sisis.de> Message-ID: <4A1FE953.90309@FreeBSD.org> Matthias Apitz wrote: > As said already, recording from the mic jack for the headset works fine > (even without local echo to headset or loudspeaker). How could I record > from the built-in mic, i.e. without the headset plug'ed in into the mic > jack? Have you tried to use pcm1/dsp1/mixer1 devices? > I'm attaching 'dmesg | fgrep pcm' as well. Thanks for a hint. > > pcm0: at cad 0 nid 1 on hdac0 > pcm1: at cad 0 nid 1 on hdac0 > pcm2: at cad 0 nid 1 on hdac0 This is not verbose output! Real verbose output `|grep pcm` includes several pages! -- Alexander Motin From guru at unixarea.de Sat May 30 14:03:38 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat May 30 14:03:45 2009 Subject: X.org nv driver (xf86-video-nv-2.1.13) && Quadro FX 770M && dual screens Message-ID: <20090530140335.GA4500@current.Sisis.de> Hello I'd like to use the external display of my Dell M4400 as a second X display screen, with lower resolution, to connect a beamer to it and to be able to direct X applications to use it with ... -display :0.1 or even just to drag the application to the second display. I have no idea how to configure this. Anyone has any pointer for me where to start reading about this? Is this possible at all with the Quadro FX 770M and the xf86-video-nv driver? The main display on LCD runs with 1920x1200 and I don't have a beamer supporting this resolution. Thanks in advance. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From henry.hu.sh at gmail.com Sun May 31 19:47:03 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Sun May 31 19:47:11 2009 Subject: X.org nv driver (xf86-video-nv-2.1.13) && Quadro FX 770M && dual screens In-Reply-To: <20090530140335.GA4500@current.Sisis.de> References: <20090530140335.GA4500@current.Sisis.de> Message-ID: <53a1e0710905311219h2e7fe9c5o4ffb913e4902226f@mail.gmail.com> On Sat, May 30, 2009 at 10:03 PM, Matthias Apitz wrote: > > Hello > > I'd like to use the external display of my Dell M4400 as a second X display > screen, with lower resolution, to connect a beamer to it and to be able to direct > X applications to use it with ... -display :0.1 or even just to drag the > application to the second display. I have no idea how to configure this. > Anyone has any pointer for me where to start reading about this? Is > this possible at all with the Quadro FX 770M and the xf86-video-nv > driver? The main display on LCD runs with 1920x1200 and I don't have a > beamer supporting this resolution. You may try the nvidia driver, since I know that you can use nvidia-settings to setup such things easily. > > Thanks in advance. > > ? ? ? ?matthias > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" >