Re: "screen" alternative
Greg, According to Freshports, the screen package is the problem. You should be able to compile from source within ports with no problems (that's what I am currently doing). /# cd /usr/ports/sysutils/screen /usr/ports/sysutils/screen# make install clean Freshports link: http://www.freshports.org/sysutils/screen/ -- Alan Gerber Grzegorz Danecki wrote: Hi List! I'm running 5.4 Stable and I'm looking for something, that can let me detach my session leaving my software running. First thought - "screen", but hey, there is no screen package in ports collection :( Google says something that it was removed due to high cpu utilization few releases ago. Is this true? Are there any alternatives? Because as I can remember screen was frequently used and highly appreciated application. Or should I rather look for some sources instead of package? Any problems with that? Many thanks in advance, You are doing great work here! Greg Danecki ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sound on Dell D600 laptop
Sound works beautifully on my D600. Unfortunately, I don't have it in front of me at work. But from what I remember, all you need to do is load the snd_ich driver via kldload(8). Alternatively as Doug mentioned, you can place the line into /boot/loader.conf to make the system load the driver at startup. The proper driver as I recall is snd_ich, so you'll need to use the line: snd_ich_load="YES" -- Alan Gerber Doug Poland wrote: On Thu, January 12, 2006 12:15, Li, Qing wrote: Has anyone successfully gotten the sound to work on the Dell D600 laptop running FreeBSD 6.0? If you've done it, could you please share your tricks with me. I've got a C600 laptop working with sound. Not sure if it's the same, but I added the following line to my /boot/loader.conf snd_maestro3_load="YES" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
wpa_supplicant setup problems
plicant.conf, but it had no effect. So, I'll ask you guys - any ideas on what I can do to make this work properly? Ideally, I'd like to make wpa_supplicant look for the home ssid with the defined PSK, and if it fails to authenticate using that, then fall back to plaintext mode. -- Alan Gerber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bizar problem with a Dell latitude D600's onboard nic
ux or XP the problem is there anyway, I just wanted to ask a question ... not start a flame war Greetz, Philip * REPLY SEPARATOR * On 10/11/2005 5:29:42 PM, Gerard Replied: I am sorry, perhaps I am not fully comprehending your post. I thought you meant that after you swapped disks, the problems subsided. //quote// So I switched disks with a colleage and lo and behold my bsd-disk in his laptop: no problem, his disk in my laptop: no problem... //end quote// I assumed that the problem stopped. Technically, if it is a hardware problem, and that does not seem to be true at this point, it is not Dell's problem if you are using an OS other than what they certified the machine to be compatible with. Example: I had an old Compaq 5140 machine that had no problems with ACPI under Windows, but failed to utilize that function under FreeBSD. There was no way I could get Compaq to correct the situation since they never certified the machine to work with anything other than Windows. Anyway, I hope you can bring this situation to a satisfactory conclusion. I've got a D600 that used to have 5.2.1 on it -- I never had any troubles with the onboard NIC. Two points of thought: what happens if you rebuild the kernel and world and "reinstall" them? Does the problem persist? Additionally, if you drop in Knoppix or some other Linux-on-CD solution, do you experience any problems? -- Alan Gerber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: re vlc 0.8.2 compile errors on 5.4
nbco wrote: Hi List, I am having problems compiling vlc 0.8.2 on 5.4. I can add it as a package but when portupgrade or portmanager tries to update it. I get the following compile error: [Error text snipped] I also am experiencing this problem, but I've developed a workaround, as de/reinstalling doesn't seem to do anything, as well as making distclean. The problem occurs within the smb access module of vlc. Navigate to /usr/ports/multimedia/vlc and do a "make config" to get to the options menu, then uncheck the smb module. Accept the changes and do a "make install" and things will work for you. I'm no expert, but I'm guessing that removing the smb functionality in this manner will prevent one from directly accessing smb shares via the vlc interface. If you fall into this situation, I'd suggest mounting the share via mount_smbfs. -- Alan Gerber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager loop?
I'd like to report a similar problem with the linux_base system. My
box has been recompiling linux_base-rh-7.3 for 12 hours now! :-)
The three strikes method sounds like a good temporary fix to the
problem. Please let us know when you get it posted!
--
Alan Gerber
Michael C. Shultz wrote:
To keep everyone informed, here is how portmanager's looping problem
with XFree86 is going to be handled:
portmanager version 0.2.4_1
Adding "three strikes checking". When "make" is run on a port
it gets 1 strike, if it's made a second time it gets 2 strikes and a
warning will be printed, if it tries to build a 3rd time it gets marked
as ignore and no more attempts will be made to build it. At the end
of a portmanager -u run every port that was ignored and why it was
ignored is listed. This change doesn't solve the problem, but makes it
managable and I will have it posted before the day is over.
portmanager version 0.2.5
When a port has a second strike placed against it, instead of getting
its dependencies from /var/db/{portname}/+CONTENTS (which is very fast)
the port's dependencies will be retrieved by running "make
all-depends-list" in the port's directory (horribly slow) . I expect
this to be a clean fix for the looping problem but may take a few days
for codeing and testing before I can release this version.
-Mike
ps. Comments or other suggestions will be highly appreciated.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Scroll whell on FreeBSD 5.3 i386
Oops. Forgot to send this to the list. :-) Alan Gerber wrote: In my particular place, I have nothing in /etc/X11. In other words, I have not created a configuration file yet - xorg has been automatically detecting my installation just fine [with the obvious exception of the mouse wheel]. Is there a way to pull out the configuration it is currently using? -- Alan Gerber gabriel wrote: You have to edit /etc/X11/ and make the change there if I remember correctly. Cheers! On Mon, 24 Jan 2005 14:59:51 -0500, Alan Gerber <[EMAIL PROTECTED]> wrote: If one is using the auto-configure feature of xorg, how does one specify this override? If there is no way to override this setting [so that one must create an xorg.cfg file, is there a way to pull out the currently-running configuration? -- Alan Gerber Andrew Hall wrote: Add this to your mouse section, and restart X. Option "ZAxisMapping" "4 5" Drew Michael Madden wrote: What is the secret to getting my scroll wheel working on FreeBSD 5.3? If have the following added to /etc/rc.conf: moused_enable="YES" moused_flags="" moused_port="/dev/psm0" moused_type="auto" I've also got the mouse section of /etc/X11/xorg.conf setup as: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection The mouse works fine as a normal mouse (right click, left click, middle click), but the scroll wheel doesn't scroll. Thanks in advance, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Scroll whell on FreeBSD 5.3 i386
If one is using the auto-configure feature of xorg, how does one specify this override? If there is no way to override this setting [so that one must create an xorg.cfg file, is there a way to pull out the currently-running configuration? -- Alan Gerber Andrew Hall wrote: Add this to your mouse section, and restart X. Option "ZAxisMapping" "4 5" Drew Michael Madden wrote: What is the secret to getting my scroll wheel working on FreeBSD 5.3? If have the following added to /etc/rc.conf: moused_enable="YES" moused_flags="" moused_port="/dev/psm0" moused_type="auto" I've also got the mouse section of /etc/X11/xorg.conf setup as: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection The mouse works fine as a normal mouse (right click, left click, middle click), but the scroll wheel doesn't scroll. Thanks in advance, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD server(s) to backup multi-platform systems remotely
Dave McCammon wrote: --- Danny <[EMAIL PROTECTED]> wrote: [snip] I haven't caught all of this thread but I'll share what I do. I use rsync to sync file to a server for backup. 6 FreeBSD and one Win2K which have been set up to rsync at different times in the morning hours. On the Win2k machine, I have cygwin running that I use to rsync the data over every night. I think there is rsync for windows but I liked the command line capabilities that cygwin gives me. All use ssh in the rsync. So after the night rsync's, I'll have a copy of files on the backup server's harddrive and will also have a copy on tape. Tape runs in morning after all servers have sync'd. I have a similar setup: a FreeBSD file and backup server with a dedicated hard drive that holds all of my backed up data. I mount the hdd read-write at midnight each night, and I have scheduled tasks that run at 1am on 5 Windows boxes that rsync (over an SSH tunnel) specific directories that I want to keep backed up to the FreeBSD box. I also have a local rsync job that runs on the FreeBSD box that backs up various locations in that system. For the Windows boxes, I use the cwrsync package, which is really just rsync with cygwin. I sort out the directory structure on the backup drive something like this: /[boxname]/[weekly.[0-2]|daily.[0-6]]/[backup_dirs] As you can tell from the directory structure, I run 7 days of incremental backups, and I also keep 3 weeks of full backups. I have scripts that run at 12:15am to rotate the various directories around so that the incremental backups can work. I compress the weekly backups via gzip to conserve hard disk space - I use the entirety of the 300gig drive. At 6:30am, I remount the hdd as a read-only drive. I push around about 20 gigs per night when everything is all said and done, but because this all happens over a local 100mbps network, it isn't that bad. I don't currently have any provision for providing easy, automated restore functionalities to the backups, and this is only onto a single hdd and not on tape or a raid array or anything, but it is "good enough" for my backup system at home. :-) -- Alan Gerber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB flash drive support/usage
Kenneth W Cochran wrote:
Hello:
I have some questions about the little USB flash drives...
Is there a FAQ or some documentation on them? So far I haven't
found much in the Handbook or manpages. Pointers welcome. :)
I haven't done any checking, but I'm sure there is *something* in the
Handbook about them.
Do I need any driver(s) besides umass(4) & its required kernel options?
In my experience, any drive that works in Windows (2000 or XP) without
needing special drivers will work in FreeBSD. I can't say that
definitively, of course, but it has been my experience.
Any differences between 4.x and 5.x support for them?
5.x has better USB support overall, but I think there was talk about
putting effort into porting this back to 4.x. I'd suggest starting with
5.x to begin with, since it represents the next generation of the
FreeBSD system.
Apparently they come setup for a FAT32 filesystem - can I format
them for other filesystems (e.g. linux-ext2, BSD UFS/UFS2, MS
NTFS) & expect them to work reliably?
I've never tried this - why change something when it is working just fine?
Assuming they work (well) with FreeBSD, how do I properly set
them up for UFS/UFS2? Do I need to fdisk and {disk,bsd}label first?
See above response.
Any favorite/least-favorite brands/models or recommendations as
to which one(s) to seek/avoid for use with FreeBSD?
I love my Lexar Jumpdrive. I have the 512MB version, but they're up to
1GB now, IIRC.
Thanks,
-kc
--
Alan Gerber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trouble with ULE scheduler
musikcom wrote: Hello! I have some trouble with ULE scheduler. I have installed FreeBSD 5.3 When I try to use ULE scheduler (by editing GENERIC file), the message "The SCHED_ULE scheduler is broken. Please use SCHED_4BSD" message appear. I do these steps: cd /sys/i386/confOK edit GENERICOK config GENERICOK cd ../compile/GENERICOK make dependFAILURE I send copy of GENERIC, sched_ule.c files in attachment and also file out.txt Please, help!!! - http://mobile.ngs.ru/games - Java-игры для мобильников и не только... http://love.ngs.ru - Знакомства в Новосибирске [attached files removed to save bandwidth] The ULE scheduler was for all practical purposes disabled in 5.3 because of instability problems some people noticed with it - so the developers are working on fixing those bugs. In the meantime, you should continue to use SCHED_4BSD. -- Alan Gerber ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: difference between releases
Bart Silverstrim wrote: On Nov 8, 2004, at 12:47 PM, [EMAIL PROTECTED] wrote: In a message dated 11/8/04 11:54:37 AM Eastern Standard Time, [EMAIL PROTECTED] writes: on the "release", which should be a known, completed code base. All part of the experience I suppose. The whole world is in beta. Get over it. Only the open-source world. When did Windows go open source? :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" In conventional terms, yes, FreeBSD releases are something like snapshots, so you're right in that respect. However, these "snapshots"/releases are not really as much of a piece of beta software as you make it out to be. Many people download, use, and test the release prior to its actual release in order to cut down on the number of bugs in that particular release. That is the reason for the src and ports (and even doc, to a certain extent) trees freezing in the days/weeks prior to a release -- so that nothing new happens except for bugfixes and bugfixes for bugfixes and so on as necessary. This probably gives you the best set of testing you can reasonably ask for in a code base that is always being updated. So what it comes down to is that releases are snapshots of a particular CVS branch at a particular point in time that gets special attention in terms of use and testing. -- Alan Gerber ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel modules & the 5.2.1-p9 to 5.3b7 migration?
Joshua Tinnin wrote: On Sunday 10 October 2004 01:35 pm, Alan Gerber <[EMAIL PROTECTED]> wrote: Joshua Tinnin wrote: On Sunday 10 October 2004 12:47 pm, Alan Gerber <[EMAIL PROTECTED]> wrote: I recently decided to update my 5.2.1-p9 system to the latest beta to check out the improvements in ACPI code on my Dell Latitude D600 laptop. So I updated sources and went through the usual [build|install][world|kernel] procedure as described in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworl d.h tml Did you rebuild your ports? If you haven't done this, you probably should, as GCC has been updated. While you're at it you might want to remove the mapping in libmap.conf and rebuild for the new library versions in BETA7. I'm not sure if that will solve your ACPI problems, but it has to be done anyway. Yes. I have rebuilt each of my installed ports, so in theory the libmap.conf mappings should be unnecessary. The problem still persists after removing the mappings, so it doesn't look like that has an affect on the problem either way. OK, well I doubted that was it, but just wanted to check. Have you tried booting without ACPI, such as: hint.acpi.0.disabled="1" in /boot/device.hints? I realize this defeats the purpose of your updating, but it might be worth seeing if it works without it. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Yes. APM takes over in this case, and the box is usable. However, it does the same thing without booting with ACPI disabled - it merely prints out the error message noted above and goes on its merry way - there is nothing preventing me from using the system whatsoever. -- Alan Gerber ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel modules & the 5.2.1-p9 to 5.3b7 migration?
Joshua Tinnin wrote: On Sunday 10 October 2004 12:47 pm, Alan Gerber <[EMAIL PROTECTED]> wrote: I recently decided to update my 5.2.1-p9 system to the latest beta to check out the improvements in ACPI code on my Dell Latitude D600 laptop. So I updated sources and went through the usual [build|install][world|kernel] procedure as described in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.h tml Did you rebuild your ports? If you haven't done this, you probably should, as GCC has been updated. While you're at it you might want to remove the mapping in libmap.conf and rebuild for the new library versions in BETA7. I'm not sure if that will solve your ACPI problems, but it has to be done anyway. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Yes. I have rebuilt each of my installed ports, so in theory the libmap.conf mappings should be unnecessary. The problem still persists after removing the mappings, so it doesn't look like that has an affect on the problem either way. -- Alan Gerber ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel modules & the 5.2.1-p9 to 5.3b7 migration?
Kris Kennaway wrote: On Sun, Oct 10, 2004 at 03:47:30PM -0400, Alan Gerber wrote: I recently decided to update my 5.2.1-p9 system to the latest beta to check out the improvements in ACPI code on my Dell Latitude D600 laptop. So I updated sources and went through the usual [build|install][world|kernel] procedure as described in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I decided to go with the GENERIC kernel and rebuild it later with my specific options - everything built successfully and it looked like everything was going great, although I did note that I was updating much more in the mergemaster step than I was originally expecting. But I muddled through it and it finally came time to reboot into beta-7. When I did reboot, I got a pretty big surprise - it appears that the kernel can't find any of its modules. In the "Bootstrap Loader" portion of the startup sequence (I *think* it is boot2 - just before you get the beastie screen asking you if you want to start with ACPI disabled, verbose mode, safe mode, etc), it appears to load the snd_emu10k1.ko and sound.ko modules. I'd expect this since my system is equipped with that style sound card. However, just after the beastie screen goes away to allow the boot to continue, I get the message "ACPI autoload failed - no such file or directory" as the first line of text, before any of the other kernel-outputted text. A couple of other interesting messages follow. One tells me that kldload can't load star_saver, reporting a "No such file or directory" error. I also get a message saying that /dev/mixer doesn't exist (and indeed it doesn't -- nor is there any sign of a sound device in the dmesg output). When I execute kldstat, I get the entries I would expect back - kernel, snd_emu10k1.ko, sound.ko, and est.ko (of the enhanced speedstep driver fame - I was running it on 5.2.1). If I try to manually load a module, such as the star_saver (this is the only thing I've done since loading acpi.ko isn't a good idea), it works. Well, where are your modules? Kris They all exist in /boot/kernel -- Alan Gerber ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mounting hard disk in multiple locations
Okay folks, help me out with this one. I'm trying to mount a single hard disk slice in two separate locations (one location being r/o and another being r/w), and having a hard time figuring out how to do it. I've tried issuing multiple mount calls, but I get a "Device busy" error. I've also checked out the mount(8) series of manpages and haven't found anything. I've also thought about trying to create a separate device node for this purpose, a la mknod, but I wanted to be sure that won't do anything overly harsh to the system before I attempt it. Any thoughts or suggestions? -- Alan Gerber ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended Motherboards for FreeBSD 4.x and 5.x
I have only used FreeBSD on one Asus board, the original A7A266. I've recently begun the undertaking of putting 5.2.1 on it. I had to disable the "Use PNP OS" function in the BIOS to make it work reliably - in other words, I'm making the BIOS assign device resources. The same is true for 4.8 and 4.9. The board does support ACPI satisfactorily, though. -- Alan Gerber >>Replied message follows Hi, personally I'm a ASUS-User. All boards i've ever used were asus except my Siemens Primergy 470 nad my Dell Latitude D600. I ran FreeBSD successfully on this boards: Asus A7M266-D, Dual-Athlon XP 1800+ (running CURRENT, ACPI w/o problems) Asus CUV4X-D, Dual-PIII 800 (ran 4.9, if i remember correctly) Asus P5A-B, K6-2 350 (running 5.2.1 p7, ACPI w/o problems) Asus A7V266-E, Athlon XP 1800+ (running CURRENT, ACPI w/o problems) and several asus borads, but never tested on freebsd, as i'm new to *NIX. asus are always high-quality boards. you'll notice that in quality of bios for example. all asus boards supporting ACPI, work flawless. Patrick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NIC-independent watchdog timeout on 5.2.1-R
Hey all, I'm trying to put 5.2.1-Release on my desktop at home, and I'm experiencing a couple of errors that have me confused. First, I get a number of "module_register: module ???/??? already exists!\nModule ???/??? falied to register: 17" errors on startup (I'm including the dmesg output which includes these errors), and I also get a watchdog timeout for all of the 4 different network cards I've used in the machine. I've used: 2x Linksys LNE100TX v4 (dc driver) 1x Generic Belkin card (rl driver) 1x Intel Pro/100 (fxp driver) My guess is that these two problems are probably related, but since I've no idea how to resolve the first problem, I started troubleshooting the second: here's what I've found so far: I've read enough of the man pages to know that this is supposedly caused by the driver not getting a response that a packet was put on the wire successfully. But I am certain that the cards are good (I've pulled all but the 1st Linksys out of working machines to test this), and the cabling and connections are all good, too. I've used the same cards successfully in WinXP with no problems whatsoever on the same machine. I am experiencing this error with the install floppies, install CD, liveCD, and even after installation via CD with the generic kernel. Disabling ACPI has had no effect in this case. I've pulled all other cards (save my video card [GeForce FX5600]) out of the machine and tried each of the above cards, but still no luck. The motherboard for the machine in question is an Asus A7A266, running BIOS revision 1011. I'm attaching the verbose ACPI-enabled dmesg output from the liveCD in case it helps. At this point I don't know what to do. I've checked the archives, FAQ, bsdforums.org, etc, and I haven't found any situations that seem to apply for me. I'm guessing that it is something about my specific hardware combination or possibly a BIOS setting, but I thought I'd check here to see if anyone had any thoughts on either a solution or a workaround. I'd appreciate any help that can be given on this situation, because I'd love to move away from running WinXP on my desktop! ;-) -- Alan Gerber 0 11 12 slot 5 0 13B 0x01 3 4 5 7 9 10 11 12 slot 5 0 13C 0x02 3 4 5 7 9 10 11 12 slot 5 0 13D 0x03 3 4 5 7 9 10 11 12 embedded06A 0x05 3 4 5 7 9 10 11 12 embedded06D 0x01 3 4 5 7 9 10 11 12 embedded02A 0x59 3 4 5 7 9 10 11 12 embedded02D 0x01 3 4 5 7 9 10 11 12 slot 6 10A 0x01 3 4 5 7 9 10 11 12 slot 6 10B 0x02 3 4 5 7 9 10 11 12 slot 6 10D 0x01 3 4 5 7 9 10 11 12 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 7 func 0 acpi0: Power Button (fixed) ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks BAD min = 2, max = 5, width = 3 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 ACPI timer looks GOOD min = 2, max = 4, width = 2 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.LNKF irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.5.0 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.5.3 \\_SB_.LNKH irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.3.0 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.3.3 \\_SB_.LNKG irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.8.0 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.8.3 \\_SB_.LNKA irq 11: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.12.0 \\_SB_.LNKB irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.12.1 \\_SB_.LNKC irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.12.2 \\_SB_.LNKD irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.12.3 \\_SB_.LNKB irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.11.0 \\_SB_.LNKC irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.11.1 \\_SB_.LNKD irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.11.2 \\_SB_.LNKF irq 0: [ 3 4 5 6 7 9 10 11 12 14 15] low,level,sharable 0.11.3 \\_SB_.LNKC irq 0: [ 3 4 5 6 7 9 10 11 12 14 15
