Re: X won't start up; No matching Device section
On Saturday 02 August 2008 02:30:22 David Gurvich wrote: Have you loaded all the kernel modules you need and installed xf86-video-chips? I am not aware of any kernel modules that i would have to load explicitely. And, yes, as indicated by the Xorg.log snippet, the chips driver is present. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X won't start up; No matching Device section
Hello List, I got an old TFT that uses a special connector to a CHIPS ct65554 graphics card. However, although the ct65554 is listed as supported, it is not recognized by the chips driver. System is FreeBSD 7-Release AMD64. I am pretty sure that the same xorg.conf worked under i386. pciconf -lvc claims device='65554 Flat Panel/LCD CRT GUI Accelerator' for the card, however although i do have an xorg.conf Device section containing Driver chips Chipset ct65554 X wont start up. Xorg.0.log complains: (II) CHIPS: Driver for Chips and Technologies chipsets: ct65520, ct65525, ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550, ct65554, ct6, ct68554, ct69000, ct69030, ct64200, ct64300 (II) Primary Device is: (WW) CHIPS: No matching Device section for instance (BusID PCI:3:7:0) found (EE) No devices detected. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shellscript conditional to check for external disk
On Saturday 21 June 2008 22:47:31 Roland Smith wrote: On Sat, Jun 21, 2008 at 09:44:09PM +, Helge Rohde wrote: Hello List, I need to write a backup script, and one of the required actions would be a copy of the backup to an external firewire drive. I would like to make this as easy as possible for the local staff, so i'd like to check whether the drive is attached, if necessary mount it, copy over the backup and unmount it again, so that the local staff can swap the external disks when they're not used. Is there a canonical way to achieve what i want? I played with the idea of simply checking for /dev/da0s1d's existance, but that won't disappear on disconnect, so that would leave the is a possibility that although da0 is in /dev, it might not be connected. Use glabel(8) to give the device an unique label. There is no telling which device /dev/da0s1d is pointing to! After labeling you can check for /dev/fstype/yourlabel, which should be unique. Make sure to unmount the drive at the end of the backup script, or you'll get a kernel panic when staff pulls the plug on a mounted device. Roland Okay, it obviosly makes sense to use glabel instead of the device node. Will the glabel appear/disappear depending on whether the drive is connected? Is it possible to have more then one physical drive with the same glabel(As i plan to utilize two identical Firewire disks) ? Either way, i still need a way to check whether a drive is attached or not. Mounting( and unmounting!) will be done from the periodic backup scripts. I am not sure how devd could help me with that, besides maybe write/delete a zero-byte file somewhere and have the periodic script check for its existence. Thank you all for your help, Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shellscript conditional to check for external disk
On Monday 23 June 2008 18:24:59 Roland Smith wrote: On Mon, Jun 23, 2008 at 05:25:58PM +, Helge Rohde wrote: On Saturday 21 June 2008 22:47:31 Roland Smith wrote: On Sat, Jun 21, 2008 at 09:44:09PM +, Helge Rohde wrote: Is there a canonical way to achieve what i want? I played with the idea of simply checking for /dev/da0s1d's existance, but that won't disappear on disconnect, so that would leave the is a possibility that although Such devices should disappear on disconnect. That's what i thought, but since i wasnt entirely sure i let the otherwise perfectly working behavior convince me otherwise. Sorry for any confusion caused. It seems that with the given Hardware combination fwohci runs into a bunch of errors and only creates the device nodes at the first time the drive is connected, but fails to destroy them upon disconnection. Reconnecting, mounting and writing to and from the device node produced no errors. If i connect the drive via usb cable instead of the fw one, all goes as expected and umass creates and destroys the device nodes. I will investigate and start a new thread on it later, for now my workaround is a strip of Gaffa Tape over the Firewire port and the instruction to only use USB ;) da0 is in /dev, it might not be connected. Use glabel(8) to give the device an unique label. There is no telling which device /dev/da0s1d is pointing to! After labeling you can check for /dev/fstype/yourlabel, which should be unique. Let me rephrase that. You should actually use the file system's utility to set a label. This works for UFS (newfs, tunefs), msdosfs (newfs_msdos), ISO9660 (mkisofs) and ntfs. Make sure to unmount the drive at the end of the backup script, or you'll get a kernel panic when staff pulls the plug on a mounted device. Roland Okay, it obviosly makes sense to use glabel instead of the device node. Will the glabel appear/disappear depending on whether the drive is connected? Yes, just like regular device nodes. I just didnt suspect just how irregular my device nodes are ;) Is it possible to have more then one physical drive with the same glabel(As i plan to utilize two identical Firewire disks) ? You can label both drives the same. I don't know what will happen it you try to connect them both at the same time. I guess that the creation of the second label will fail. Either way, i still need a way to check whether a drive is attached or not. Simple. Check for the device node. Mounting( and unmounting!) will be done from the periodic backup scripts. I am not sure how devd could help me with that, besides maybe write/delete a zero-byte file somewhere and have the periodic script check for its existence. It can't completely. It should be able to detect your labeled device and mount it somewhere. But you _have_ to unmount _before_ the device node disappears, lest you get the aforementioned panic. Thats precisely why i didnt want to let devd do the mounting: doing it just-in-time minimises the window of opportunity for vicious plug-pullers. It's easier to have the backup script test if the labeled device node exists. Do not forget to print a message (after the script has unmounted the drive) for the operators that the backup is finished and that the device may be disconnected. The Machine will run headless - I thought about sending a mail but i probably won't bother as by the time the backup and copy takes longer than a night, I should have received angry emails and snmp traps about filesystems way beyond their official capacity anyway ;) regards, Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
shellscript conditional to check for external disk
Hello List, I need to write a backup script, and one of the required actions would be a copy of the backup to an external firewire drive. I would like to make this as easy as possible for the local staff, so i'd like to check whether the drive is attached, if necessary mount it, copy over the backup and unmount it again, so that the local staff can swap the external disks when they're not used. Is there a canonical way to achieve what i want? I played with the idea of simply checking for /dev/da0s1d's existance, but that won't disappear on disconnect, so that would leave the is a possibility that although da0 is in /dev, it might not be connected. Any ideas or RTFM-pointers? Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Working at Console
Hi Graham you might want to check out audio/mp3blaster, very mature and powerful. http://www.freshports.org/audio/mp3blaster/ regards, Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GCC upgrade
On Friday 24 November 2006 16:40, Mark wrote: -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: vrijdag 24 november 2006 17:11 To: Mark Cc: freebsd-questions@freebsd.org Subject: Re: GCC upgrade I tested the new gcc, btw (compiled MySQL server with it, which takes quite a while). Seems to work fine. But I'm not enough of a C expert to know precisely how to do a safe upgrade of this kind. If you're not an expert then just leave it alone. Replacing the system compiler might sound like a cool thing to do, but what will actually happen is that you'll make your FreeBSD system unbuildable. Guess I hadn't thought about it that way. Good thinking. It's just that 2.95.4 seems so ancient. :) Only reason I wanted to in the first place, is that I've had several ports that wanted a 3.x series gcc (and kept wanting to build one). Thanks, You could leave the default in place, define a different gcc for the ports in /etc/make.conf and then just add to the list of excludes every time you run into problems while building a port. Thats what i do, and so far roughly 80% of the ports seem quite content with gcc4.2 If that sounds cool to you, checkout this sample make.conf out of some german Howto. You wont need knowledge of german, Its self explaining enough. http://wiki.bsdforen.de/index.php/Make.conf_optimieren#.2Fetc.2Fmake.conf have fun, Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
