new buildworld brings most of the notebook back to work
after doing the make buldworld/buildkernel/installkernel/installworld again today CEST 10:00 most of my notebook works again: i got the floppy back i recompiled rtc/vmware2 after downloading the ports again and rtc/vmware loads and works fine now sbc recognices my ESS1879 (kde2 still doesnt play sound, but it is recogniced) the edimax 4000 pcmcia adapter works fine (needed to remove irq 5 in pccard.conf and set io to 280 instead of 240) now the open problems are only a few: rebooting doesnt work. not with shutdown -r now and not with reboot. i need to do a shutdown -h now, power off/on and the pc starts fine. to make sure the notebook works i used another disk and installed 4.1 on it from the cd set. with this rebooting works just fine. i compiled my kernel for the notebook, rebooting still works fine. as far as i remember till cvsup somewhere around the 17th i was able to reboot with 4.1. then 4.1 had the same problem as i have now with current too. pressing any key after shutdown -h now brings the same result. immediatly black screen (before any bios message) and hangs forever. the second problem cant be really verified at the moment. because suspend/resume works like the reboot. best regards, Karl __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Majordomo Problem
After installing the majordomo port I get the following message: May 31 04:04:26 n669 sendmail[66642]: EAA66641: SYSERR(root): hash "Alias1": missing map file /usr/local/majordomo/aliases.majordomo.db: No such file or directory a newaliases begets this: freebsd:/etc# newaliases /etc/aliases: 41 aliases, longest 56 bytes, 784 bytes total hash map "Alias1": unsafe map file /usr/local/majordomo/aliases.majordomo.db: Permission denied WARNING: cannot open alias database /usr/local/majordomo/aliases.majordomo Cannot create database for alias file /usr/local/majordomo/aliases.majordomo But, believe you me, the /usr/local/majordomo/aliases.majordomo *is* present, and I am running as root. thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -Current + X 4.0.1 = mouse problems
Christian Weisgerber wrote: > > Doug Barton <[EMAIL PROTECTED]> wrote: > > > Previously I had X + moused working just fine, so I had the best > > of both worlds. With X 4.0.1 if I use moused I get no response from the > > mouse in X at all. > > Make sure you use > > Option "Protocol" "MouseSystems" > > Protocol "Auto" is not reliable. I had XFree86 4.0.1 lock my system up completely if the options "auto" & "/dev/sysmouse" were present - the screen would go blank, no keyboard or mouse response, and a hard reboot was required to get out of it. This is running a reasonably recent 5.0-CURRENT and I actually thought it may have something to do with resource locks as X worked fine if I used "auto" & "/dev/psm0" without `moused' present. Your suggestion has everything working fine now, though. Much appreciated. Regards, Trent. > > -- > Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Majordomo Problem
jwright> freebsd:/etc# newaliases jwright> /etc/aliases: 41 aliases, longest 56 bytes, 784 bytes total jwright> hash map "Alias1": unsafe map file jwright> /usr/local/majordomo/aliases.majordomo.db: Permission denied WARNING: cannot open alias database /usr/local/majordomo/aliases.majordomo Cannot create database for alias file /usr/local/majordomo/aliases.majordomo jwright> But, believe you me, the /usr/local/majordomo/aliases.majordomo *is* jwright> present, and I am running as root. This is covered in the FAQ: http://www.sendmail.org/faq/section3.html#3.32 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MajorCool
Does anyone know the default password for majorcool if you install the FreeBSD port? thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
smbus PCI device?
I'm trying to understand this iic/smbus stuff in order to write a driver for some new hardware. The PCI bus shows this device: found-> vendor=0x8086, dev=0x2413, revid=0x02 class=0c-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=b, irq=10 map[20]: type 1, range 32, base fe00, size 4 The class/sub-class/programming interface (highlighted above) indicates a SMBus device as specified by PCI 2.2. However, I'm not sure what that is. Adding the "smbus" device and friends to the kernel config doesn't cause this device to be detected. You'd think all I needed to do then would be to add the device ID to a list in the smbus driver somewhere, but I can't find that list. Does "smbus_pci.c" not exist yet? Of course, you can't download the PCI 2.2 spec without being a "member". Am I going down the right path trying to write a driver for this device? Thanks, -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/modules vs. /boot/kernel
Hi, Just a heads up on a minor problem I ran into... I've had a system running 5.0-current from about 3 months ago... that system kept modules in /modules. After upgrading to -current as of today, vinum would nolonger load, complaining about: link_elf: symbol tsleep undefined Well, kldload -v vinum also complained... and sysctl reports: kern.module_path: /boot/modules/;/modules/;/boot/kernel/ To make a long story short, there was an old vinum module in /modules from the previous system/kernel. After rm'ing the /modules area everything works again. Question, is /modules still valid? I haven't seen any real discussion of it amoungst the kernel discussions... -John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /modules vs. /boot/kernel
On Tue, Sep 26, 2000 at 10:04:34PM -0400, John DeBoskey wrote: >Question, is /modules still valid? Yes. It should be used for 3rd party modules only. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: Avoiding version checking of CD-ROM (patchincluded)
jkh> Thanks for reminding me to go look at that code - you're right, jkh> the check is incorrectly done and insufficiently general. Fixed jkh> in -current and -stable! Very glad to hear that... thank you. Today is Wednesday and 3-stable build will run at current.jp.FreeBSD.org. If it goes successfully, I'll put cdrom.inf file to the triplex CD-ROM (yeah!). Speaking about sysinstall, would you please check my PR (bin/21423, http://www.freebsd.org/cgi/query-pr.cgi?pr=21423>) ? Maybe there are few people who want to install -CURRENT to a fresh PC (too crasy ?:-), but when we want to release 5.0-RELEASE, it would be a big problem. It should be considered also that where is the best location for *GENERIC* kernel image (/boot/kernel/kernel.GENERIC is a good candidate). -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/21423: Can't load kernel, after rebooting fresh-installed5.0-CURRENT
Here is a status report of this PR. To announce more wider audiences, this mail is also sent to [EMAIL PROTECTED] * This PR keeps all committers away. No lucks. * If you want to install 5.0-CURRENT to a *fresh* PC, you'll be warned that your PC cannot find the kernel location. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
