Virtual FreeBSD
Can anyone tell me exactly what Virtual FreeBSD is? If I Google the term, I get a whole bunch of help webpages from various web hosting outfits. What's spooky is all of the sites have the same content. That definately gives me the impression someone is selling a product called Virtual FreeBSD based off of, you guessed it, FreeBSD. I'm trying to figure out exactly what this Virtual FreeBSD is and how it differs from the vanilla FreeBSD. Unfortunately, any information about Virtual FreeBSD itself is being drowned out by the web hosters' help and marketing pages when I search. Anyone have any information or pointers? Like who is the vendor for a start? -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Virtual FreeBSD
On Thu, Jul 17, 2003 at 03:27:06PM -0700, Rus Foster wrote: On Thu, 17 Jul 2003, Crist J. Clark wrote: Can anyone tell me exactly what Virtual FreeBSD is? If I Google the term, I get a whole bunch of help webpages from various web hosting outfits. What's spooky is all of the sites have the same content. That definately gives me the impression someone is selling a product called Virtual FreeBSD based off of, you guessed it, FreeBSD. I'm trying to figure out exactly what this Virtual FreeBSD is and how it differs from the vanilla FreeBSD. OK as one of those companies that offer Virtual FreeBSD it is normal FreeBSD. However what we basically do is run a jail on top of FreeBSD itself offering a virtual machine i.e. Virtual FreeBSD I figured it was jail(8) or a suped up, customized jail. So where is everyone getting this exact same set of documentation? http://support.securesites.com/support/virtual/freebsd/ http://www.2kweb.net/support/virtual/freebsd/ http://iasweb.com/support/docs/virtual/freebsd.html http://www.vpshosting.net/support/virtual/freebsd/ http://www.aplonis.com/support/virtual/freebsd/ http://www.perilpoint.com/support/virtual/freebsd/ -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Virtual FreeBSD
On Thu, Jul 17, 2003 at 04:22:35PM -0700, Rus Foster wrote: Hi, I figured it was jail(8) or a suped up, customized jail. So where is everyone getting this exact same set of documentation? http://support.securesites.com/support/virtual/freebsd/ http://www.2kweb.net/support/virtual/freebsd/ http://iasweb.com/support/docs/virtual/freebsd.html http://www.vpshosting.net/support/virtual/freebsd/ http://www.aplonis.com/support/virtual/freebsd/ http://www.perilpoint.com/support/virtual/freebsd/ If you look at all those domains they are hosted either by secure.net or bestserver.net. I would guess that these are linked at some level so really I wouldn't be surprised if this was the same company or some form of reseller Upon closer inspection, I think they're all Verio resellers. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Win2k to racoon Cookbook
I know I've seen multiple howto's and mails describing how to do this
in the past, but the heck if I can Google one or pull one out of the
archives at the moment.
I have Win2k at one end and FreeBSD/racoon on the other. The Win2k
systems aquire addresses by DHCP. I've seen documents describing how
to do,
Win2k { Internet } FreeBSD/racoon { Private Net }
||
VPN tunnel
But like I said, I'm coming up dry. I've got certs set up, and racoon
will do cert (rsasig) authentication with other racoon peers. I need
help with the Win2k end.
I should mention that I'm kind of trying to do the reverse. I really
am doing,
{ Private Net }
Win2k -- { Wireless } |
FreeBSD/racoon - {LAN } -- FreeBSD/racoon -- { Internet }
|___|
VPN tunnel
I am trying to secure my wireless LAN by doing IPsec since WEP is
hopelessly broken (and since I can't figure out how to get Win2k and
FreeBSD to use the same keys).
The FreeBSD/racoon to FreeBSD/racoon is up and I must say, is rely
cool. Now if I could get the Win2k running over IPsec, it would be
great. Where'd those howto's get to? Anyone got something like this
going?
--
Crist J. Clark | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: arplookup xx.xxx.xx.xxx failed: host is not on local network
On Wed, Sep 18, 2002 at 02:55:32PM -0400, Jim wrote: This is a very good explanation, however I have this identical scenario with one of my co-los. I have gone round and round with the administrator for over a year now with no solution. You make the statement below that these two machines can't communicate, however I can ping and tracroute the offending machines, and they can do the same in reverse. On traceroute, the traffic definitely travels through the router as it should, but I still see these out of network ARP requests. I know I'm confused :( Actually, the communications can work depending on the situation. You can get some asymetric routing going where the machine with the smaller netmask is bouncing everything through a router and the other machine is talking back directly. The router is often, but not always, going to be generating ICMP redirects in such a scenario. They are another marker for this kind of misconfiguration. In your example, make sure to not only run traceroute(8), but run a tcpdump(8) too with the '-e' option. Check the MACs to see if the responses are _really_ coming back through the router. Remember, a traceroute(8) shows you the route packets take to get to a remote host. It tells you nothing about the route they take back. [Inappropriate cross-post to -stable removed.] On Sun, Sep 15, 2002 at 02:08:51PM -0500, Chris Byrnes wrote: My /var/log/messages is being filled, non-stop, by these errors looped: Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed: host is not on local network Sep 15 13:41:28 servername /kernel: arplookup xx.xxx.xx.xxx failed: host is not on local network After doing some reading, I've already issued, sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 thinking that would fix the problem. Unfortunately, it has not. Any ideas? This is a netmask problem, but not really the one that other people have described. This is how it usually works. Your troubled machine above, servername, receives an ARP who-has from another machine on the LAN called clientname. However, the IP address that clientname gives as a source does not match up to any local networks that servername knows about. For example, say servername has an address of 192.0.2.10/25. The other machine has 192.0.2.210/24. When servername gets an ARP (which is broadcast so servername gets it fine), who-has 192.0.2.10 tell 192.0.2.210 It gets confused. 192.0.2.210 is not local (as far as it is concerned) so it logs an error. Note that this is not a harmless error. These two machine cannot talk to each other. The fix, of course, is to make sure all machines on the same LAN have the same netmask. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: monitor ALL connections to ALL ports
On Mon, Oct 14, 2002 at 05:09:43PM -0500, Maildrop wrote: On Mon, Oct 14, 2002 at 02:31:05PM -0500, Maildrop wrote: I put these rule in: ipfw add count log all from any to any I am getting messages in my log (/var/log/all.log) that appears like this: Oct 14 14:15:06 hydra /kernel: Connection attempt to UDP 192.168.17.1:161 from 192.168.17.1:1166 That's a log_in_vain message, not ipfw(8). Which is exactly, what I want, but there is a couple isses: 1) It only logs failed connects. If I try to `telnet localhost 55`, it will log that, but if I do a `telnet locahost 80` (where web server is running) the connection is valid and doesn't log it. Right, that's how log_in_vain works. (from tcp(4)) tcp.log_in_vainLog any connection attempts to ports where there is not a socket accepting connections. The value of 1 limits the logging to SYN (connection establishment) packets only. That of 2 results in any TCP packets to closed ports being logged. Any value unlisted above disables the logging (default is 0, i.e., the logging is disabled). '1' is limited to connection established (valid connections) No, it's limited to SYN's at _closed_ ports. Read the first sentence again, Log any connection attempts to ports where there is not a socket accepting connections. and '2' is limited to connection failed... how do I get both failed AND established from log_in_vain? I want to log all connections, regardless if they failed or successed, regardless if they have a daemon running on that port or not. log_in_vain doesn't do connections to listening ports. That's the job of what ever is listening. Currently, they are both set as '1': net.inet.tcp.log_in_vain: 1 net.inet.udp.log_in_vain: 1 2) How do I setup Syslog for this? ipfw man page says it logs to LOG_SECURITY facility. I want to log all connections (failed or not), into one file.. This is what I currently have in my syslogd.conf file (the log above I am pulling from all.log): security.* /var/log/security log.security/var/log/ipfw.log Both these files are empty :( I restarted syslogd. The second one should give you an error. The first one should catch ipfw(8) logging. You did rebuild your kernel with IPFIREWALL and IPFIREWALL_VERBOSE, right? [snip] Something weird that I found: hydra# ipmon -D /var/log/ipfw.log /dev/ipl: open: Device not configured hydra# file /dev/ipl /dev/ipl: character special (79/0) hydra# grep ipmon /etc/rc.conf ipmon_enable=NO # Set to YES for ipmon; needs ipfilter or ipnat ipmon_program=/sbin/ipmon # where the ipfilter monitor program lives ipmon_flags=-Ds # typically -Ds or -D /var/log/ipflog Is ipmon part of ipfw? No, it's part of IPFilter. Here's your problem, hydra# ipfw list 00050 divert 8668 ip from any to any via dc1 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any 65100 count log logamount 100 ip from any to any 65535 deny ip from any to any How is anything ever going to reach rule 65100? 65000 passes everything. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: upgrading problem
On Mon, Oct 21, 2002 at 10:07:50PM -0400, Lowell Gilbert wrote: Hongbo Li [EMAIL PROTECTED] writes: I have upgraded my box from 4.6-stable to 4.7-stable today. Everything seemed OK. When I ran the command uname -a,the system reported ...4.7-stable But when I ran the command man cat, at the end of the manual, the system reported FreeBSD 4.6. Why? BTW, the option my cvsup file used was src-all. That man page hasn't been changed since FreeBSD 4.6, so the version listed in it hasn't changed either. Uh, no. That's not how it works. And the manpage hasn't changed since before 4.5-RELEASE. More likely, the original poster has old cat pages lying around that aren't getting updated for some reason. Look in /usr/share/man/cat1. Or perhaps you didn't actually get everything installed correctly? What do the dates in /usr/share/tmac look like? -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
m4 Problems
I want to do something that I _think_ should be rather simple within m4(1). I want to test if a macro value has been set. If it is set, I want to modify it and continue. If it is not set, I want to produce an error message and bail out. However, it is not working. Here is an example of a test script, $ cat testerr.mc ifdef(`TEST', ``TEST' defined.', `TEST not defined.') ifdef(`TEST', define(`TEST', `NEW'TEST), errprint(`TEST not specified, exiting.') m4exit(1)) The value of `TEST' is TEST. Now I run it without TEST set, $ m4 testerr.mc TEST not defined. TEST not specified, exiting. $ echo $? 1 And it looks good. But now I try with TEST set, $ m4 -D TEST=test testerr.mc TEST defined. TEST not specified, exiting. $ echo $? 1 And it acts as if it is NOT set. It looks like the third argument of the second ifdef macro is getting evaluated even though the first argument is not set. So, I'll try this test script instead, ifdef(`TEST', ``TEST' defined.', `TEST not defined.') ifdef(`TEST', define(`TEST', `NEW'TEST), `errprint(`TEST not specified, exiting.') m4exit(1)') The value of `TEST' is TEST. And try the set case, $ m4 -D TEST=test testerr.mc TEST defined. The value of TEST is NEWtest. $ echo $? 0 And it works! OK, now check the case where it is not set, $ m4 testerr.mc TEST not defined. The value of TEST is NEWTEST. $ echo $? 0 So now this case doesn't work. What quoting scheme do I need to use here to get this to work correctly? Or is there some other trick to it? Can someone explain m4(1)'s order of evaluation and what actually gets evaluated in each case? -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD IPFW/IPFILTER sysctl MIB's
On Sun, Dec 07, 2003 at 11:49:42AM -0500, fbsd_user wrote:
[snip]
How's it goin', fbsd_user? Been a while.
The question is, who get access to the packets first, these MIB's
or the firewall?
There is no simple answer to this. The MIB values affect behaviors
within the kernel. The important parts of ipfw(8) and ipf(8) are code
inside of the kernel. The some of the behavior of ipfw(8) and ipf(8)
themselves are controlled by sysctl(8) knobs,
net.inet.ip.fw.enable
net.inet.ip.fw.one_pass
net.inet.ip.fw.debug
net.inet.ip.fw.verbose
...
net.inet.ipf.fr_flags
net.inet.ipf.fr_pass
net.inet.ipf.fr_active
net.inet.ipf.fr_tcpidletimeout
...
Whether a specific entry in the sysctl(8) MIB has an effect felt
before a packet gets to ipfw(8) or ipf(8) processing depends on that
specific entry.
And just because the feature enabled by the sysctl(8) knob occurs
after firewall processing does not mean it is useless. Packets that
are allowed through the firewall still will be affected by their
settings. For example, you set net.inet.tcp.drop_synfin and have a
rule like,
02000 pass tcp from any to ${smtpsrv} 25
For your mail server. You do not need to add an explicit drop rule for
SYN+FIN packets in your firewall rules (or more likely, you are
protected if you forget such a rule).
--
Crist J. Clark | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: `pkg_info | grep -i openssh` ; echo 2.9 vs 3.0.2? [cjc]
On Wed, Apr 10, 2002 at 02:35:16AM -0400, Peter Leftwich wrote: On Mon, 8 Apr 2002, Crist J. Clark wrote: [snip] PL My question was regarding ssh, not sshd. Then I shall reprhase: Are you actually running the ssh(1) in /usr/local/bin/ssh or the old one in /usr/bin/ssh? Crist J. Clark | [EMAIL PROTECTED],[EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] I apologize for being snippy, if I seemed so. You alone fixed my woes!!! :) # ssh -V OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, OpenSSL 0x0090601f # which ssh /usr/bin/ssh # /usr/local/bin/ssh -V OpenSSH_3.0.2, SSH protocols 1.5/2.0, OpenSSL 0x0090601f # mv /usr/bin/ssh /usr/bin/ssh_2.9_old_dont_use # ln -s /usr/local/bin/ssh /usr/bin/ssh I guess that last line isn't really necessary if I adjust my $PATH, huh? Probably, the cleanest thing to do is define a shell alias (assuming you use a shell that supports them), $ alias ssh /usr/loca/bin/ssh Would be the csh(1)-ish way to do it. -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-security in the body of the message ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: `pkg_info | grep -i openssh` ; echo 2.9 vs 3.0.2?
On Sun, Apr 07, 2002 at 12:00:55AM -0800, Peter Leftwich wrote: prompt$ pkg_info | grep -i openssh openssh-3.0.2 OpenBSD's secure shell client and server (remote login prog I just upgraded (or tried to upgrade) openssh on my FreeBSD 4.5-RELEASE box using /stand/sysinstall but I get this (ver. 2.9??) when I type: prompt$ ssh -V OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, OpenSSL 0x0090601f Did you actually change the rc.conf(5) file to start the new daemon, which probably lives in /usr/local/sbin/sshd, rather than the old one in /usr/sbin/sshd? -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/| [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-security in the body of the message ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Recovering Trashed Filesystems
I have two file systems in very sad shape that I would like to retrieve some files from. I've net booted the sick box and can access the two bad UFSs. One file system, the root file system, isn't too bad off. However, the usr directory is messed up. I can do, # ls .cshrc bootlib proctmp .profiledev libexec rescue usr .snap entropy lost+found rootvar COPYRIGHT etc media sbin bin homemnt sys But if I try look at the files (directories), # ls -l ls: lib: Bad file descriptor ls: usr: Bad file descriptor ls: var: Bad file descriptor total 52 -rw-r--r-- 2 root wheel 787 Jun 25 2008 .cshrc -rw-r--r-- 2 root wheel 253 Jun 20 2008 .profile drwxrwxr-x 2 root operator 512 Jun 27 2008 .snap -r--r--r-- 1 root wheel 6188 Jun 20 2008 COPYRIGHT drwxr-xr-x 2 root wheel 1024 Jun 20 2008 bin drwxr-xr-x 8 root wheel 512 Jun 28 2008 boot dr-xr-xr-x 2 root wheel 512 Jun 28 2008 dev -rw--- 1 root wheel 4096 Nov 26 2008 entropy drwxr-xr-x 20 root wheel 2560 Jun 19 22:35 etc drwxr-xr-x 2 root wheel 512 Jun 25 2008 home drwxr-xr-x 2 root wheel 512 Jun 20 2008 libexec drwx-- 2 root wheel 2048 May 23 07:47 lost+found drwxr-xr-x 2 root wheel 512 Jun 20 2008 media drwxr-xr-x 2 root wheel 512 Jun 20 2008 mnt dr-xr-xr-x 2 root wheel 512 Jun 20 2008 proc drwxr-xr-x 2 root wheel 2560 Jun 20 2008 rescue drwxr-xr-x 4 root wheel 512 Jul 27 21:26 root drwxr-xr-x 2 root wheel 2560 Jun 20 2008 sbin lrwxr-xr-x 1 root wheel 11 Jun 20 2008 sys - usr/src/sys drwx-- 2 root wheel 512 Jun 26 2008 tmp We see usr is messed up. And what I'd like to recover are files up in usr/local/etc. Now I can mount -r /dev/ad0s1a /mnt to get the above results, but fsck /dev/ad0s1a returns, # fsck /dev/ad0s1a ** /dev/ad0s1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y 32 is not a file system superblock SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE -b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8). Some help on recovering the files? I don't need the whole disk intact. As I said, I just want to track down some local stuff in usr/local/etc. As for the second file system, the var file system, it is more messed up. Looks like big chucks are zeroed out. But again, there are a few files I would like to recover. I have managed to recover one important one by running, # dd if=/dev/ad0s1f | hexdump -C | more And manually finding the file and then using, # dd if=/dev/ad0s1f skip=m count=n /tmp/recovered.txt Then manually editing. But that is too labor intensive to try to grab everything. Again, when I fsck(1) I get the same message as above. Anyone have tools for recovering files from these broken file systems? -- Crist J. Clark | cjcl...@alum.mit.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Recovering Trashed Filesystems
On Fri, Jul 31, 2009 at 12:00:46PM +0200, Polytropon wrote: On Thu, 30 Jul 2009 23:46:50 -0700, Crist J. Clark cristcl...@comcast.net wrote: [snip] We see usr is messed up. And what I'd like to recover are files up in usr/local/etc. Now I can mount -r /dev/ad0s1a /mnt to get the above results, but fsck /dev/ad0s1a returns, # fsck /dev/ad0s1a ** /dev/ad0s1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y 32 is not a file system superblock SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE -b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8). You could try do locate superblocks using this command: Err... Hmmm. Seems to be something missing here? Install the port ffs2recov and use its -s and -p options. Refer to the excellent manpage. I got ffs2recov(1) and it would seem to be exactly what I need, but it's not working so well for me. I ran it with -s and it found some superblocks, superblock: 116113408(byte), 226784(block), cg: 116129792(byte), 226816(block), 10(nth), fs begin: 18446744073706014720(block), primary sb at: 18446744073706014848(block) superblock: 147439616(byte), 287968(block), cg: 147456000(byte), 288000(block), 2(nth), fs begin: 18446744073709086720(block), primary sb at: 18446744073709086848(block) superblock: 308805632(byte), 603136(block), cg: 308822016(byte), 603168(block), 11(nth), fs begin: 18446744073706014720(block), primary sb at: 18446744073706014848(block) superblock: 340131840(byte), 664320(block), cg: 340148224(byte), 664352(block), 3(nth), fs begin: 18446744073709086720(block), primary sb at: 18446744073709086848(block) ... But if I try to access that superblock as specified in the documentation, net5501# ffs2recov -o 226784 -p /dev/ad0s1f get_sblock: Bad magic (0) It doesn't work, but if I try it with bytes rather than blocks, net5501# ffs2recov -o 116113408 -p /dev/ad0s1f magic 19540119 (UFS2) timeFri Jun 27 20:36:13 2008 superblock location 65536 id [ 4865b1ad c24cb822 ] ncg 21 size1970116 blocks 1907915 ... That makes me nervous. Anyway, I don't seem to be getting very far. ffs2recov(1) would seem to be exactly the thing I need, but it's not finding any files. [snip] Finally, may I ask if you have any ideas about what caused this problem? Oh, yeah. The file systems reside on flash memory. I've been having issues with it for some time. It was bad enough that I couldn't get good dump(8)s of the file system for quite a while and running stuff like that made it more unstable. I did manual backups periodically of files that were more important, but of course, it failed right before I was due to make backups but after I had made a few changes earlier in the week. Once I recover all I can, I'll go spend another whopping $20 on a few gig of flash at Fry's. Right now, I'm net booting the sick little box in question. -- Crist J. Clark | cjcl...@alum.mit.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Xorg and WSXGA
I finally dumped the CRT and bought a ridiculusly cheap 20 LCD monitor. Works great except I'm having problems getting it to go widescreen and use the full display area. I followed the instructions of section 5.4.3.2 of the Handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html But I'm not getting anywhere. The Xorg logs always say, (II) I810(0): Not using driver mode 1680x1050 (bad mode clock/interlace/doublescan) For the widescreen resolution. The printed documentation with the monitor says it does 1680x1050 at 65.29 kHz horizontal and 60 Hz vertical, and the probed DDC gives, (II) I810(0): Modeline 1680x1050 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (II) I810(0): Modeline 1680x1050 146.25 1680 1960 2136 2240 1050 1053 1059 1089 +hsync -vsync But I still get the error. Manually adding the numbers to the xorg.conf gives the same results. So what do I try next? Attached are the Xorg.0.log and the xorg.conf. Again, the monitor works fine in other modes, but I want to use widescreen. As the probed info from the xorg.conf indicates, the graphics card is an Intel i810 family. The new monitor is an Envision G2016wa. Thanks for any help. -- Crist J. Clark | [EMAIL PROTECTED] X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD goku.pumpky.net 6.2-STABLE FreeBSD 6.2-STABLE #0: Fri Feb 16 11:58:12 PST 2007 [EMAIL PROTECTED]:/home/cjc/obj/usr/src/sys/GOKU i386 Build Date: 08 August 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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 Oct 29 08:10:23 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) 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/ (**) RgbPath set to /usr/local/share/X11/rgb (**) ModulePath set to /usr/local/lib/xorg/modules (II) Loader magic: 0x819e340 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.1 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: pcidata (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.2.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.1 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7124 card 1028,00b4 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7125 card 1028,00b4 rev 03 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev 02 class 0c,05,00 hdr 00 (II) PCI: 01:07:0: chip 1274,1371 card 1274,1371 rev 06 class 04,01,00 hdr 00 (II) PCI: 01:08:0: chip 10b7,9050 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 01:0c:0: chip 10b7,9200 card 1028,00b4 rev 78 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0006 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0xe000 - 0xe0ff (0x100) IX[B] [1] -1 0 0xe400 - 0xe4ff (0x100) IX[B] [2] -1 0 0xe800 - 0xe8ff (0x100) IX[B] [3] -1 0 0xec00 - 0xecff
Re: Xorg and WSXGA
On Tue, Oct 30, 2007 at 07:50:10PM -0400, Brian A. Seklecki wrote: On Mon, 2007-10-29 at 23:36 -0700, Crist J. Clark wrote: I finally dumped the CRT and bought a ridiculusly cheap 20 LCD monitor. Works great except I'm having problems getting it to go widescreen and use the full display area. I followed the instruction xinit -- -verbose 9 -logverbose 9 It should print out a list of modes that it _will_ validate. It doesn't really give me any useful additional information that I notice. I still don't understand why it refuses to go for 1680x1050. The log is attached. -- Crist J. Clark | [EMAIL PROTECTED] X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD goku.pumpky.net 6.2-STABLE FreeBSD 6.2-STABLE #0: Fri Feb 16 11:58:12 PST 2007 [EMAIL PROTECTED]:/home/cjc/obj/usr/src/sys/GOKU i386 Build Date: 08 August 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Wed Oct 31 22:40:31 2007 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) 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/ (**) RgbPath set to /usr/local/share/X11/rgb (**) ModulePath set to /usr/local/lib/xorg/modules (II) Loader magic: 0x819e340 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.1 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: pcidata (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=X.Org Foundation compiled for 7.2.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.1 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7124 card 1028,00b4 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7125 card 1028,00b4 rev 03 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev 02 class 0c,05,00 hdr 00 (II) PCI: 01:07:0: chip 1274,1371 card 1274,1371 rev 06 class 04,01,00 hdr 00 (II) PCI: 01:08:0: chip 10b7,9050 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 01:0c:0: chip 10b7,9200 card 1028,00b4 rev 78 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0006 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0xe000 - 0xe0ff (0x100) IX[B] [1] -1 0 0xe400 - 0xe4ff (0x100) IX[B] [2] -1 0 0xe800 - 0xe8ff (0x100) IX[B] [3] -1 0 0xec00 - 0xecff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfd00 - 0xfeff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xf900 - 0xf9ff (0x100) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:1:0) Intel Corporation 82810E DC-133 CGC [Chipset Graphics Controller] rev 3, Mem @ 0xf400/26, 0xff00/19 (II) Addressable bus resource ranges are [0] -1 0 0x - 0x (0x0) MX[B] [1] -1 0 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges
Re: Xorg and WSXGA
On Thu, Nov 01, 2007 at 07:49:42AM -0500, Josh Paetzel wrote: On Thursday 01 November 2007 12:53:11 am Crist J. Clark wrote: On Tue, Oct 30, 2007 at 07:50:10PM -0400, Brian A. Seklecki wrote: On Mon, 2007-10-29 at 23:36 -0700, Crist J. Clark wrote: I finally dumped the CRT and bought a ridiculusly cheap 20 LCD monitor. Works great except I'm having problems getting it to go widescreen and use the full display area. I followed the instruction xinit -- -verbose 9 -logverbose 9 It should print out a list of modes that it _will_ validate. It doesn't really give me any useful additional information that I notice. I still don't understand why it refuses to go for 1680x1050. The log is attached. Could you attach your xorg.conf? It looks like there is a combination of problems keeping it from doing 1680x1050. I've tried a few things, but right now, running on defaults and auto-generated configuration. -- Crist J. Clark | [EMAIL PROTECTED] Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/local/share/X11/rgb 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 extmod Load record Load dbe Load glx Load GLcore Load xtrap Load dri Load freetype Load type1 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 #DisplaySize 470 300 # mm Identifier Monitor0 VendorName ENV ModelNameG2016w ### Comment all HorizSync and VertRefresh values to use DDC: #HorizSync31.0 - 80.0 #VertRefresh 56.0 - 75.0 Option DPMS #ModeLine 1680x1050 146.2 1680 1784 2136 2240 1050 1053 1059 1089 -hsync +vsync #ModeLine 1680x1050 146.2 1680 1784 2136 2240 1050 1053 1059 1089 -hsync +vsync EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option NoAccel # [bool] #Option SWcursor # [bool] #Option ColorKey # i #Option CacheLines# i #Option Dac6Bit # [bool] #Option DRI # [bool] #Option NoDDC # [bool] #Option ShowCache # [bool] #Option XvMCSurfaces # i #Option PageFlip # [bool] # Recommended by http://gentoo-wiki.com/HOWTO_Widescreen_Resolutions_(WSXGA) Option ModeValidation NoMaxPClkCheck Identifier Card0 Driver i810 VendorName Intel Corporation BoardName 82810E DC-133 CGC [Chipset Graphics Controller] BusID PCI:0:1:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultFbBpp 24 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 # SubSection Display # Viewport 0 0 # Depth 24 # Modes 1680x1050 # EndSubSection EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CDRW Stopped Working Moving to 6.x
I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 CRD-8400B/1.06 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? -- Crist J. Clark | [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: CDRW Stopped Working Moving to 6.x
On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: Make sure you add atapicam into your kernel it is not in generic! I had the same problem. /etc/loader.conf atapicam_load=YES I did a, # kldload /boot/kernel/atapicam.ko And to reinitiallize the drive, # atacontrol detach ata1 # atacontrol attach ata1 I got the same console message, acd0: detached (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry atapicam1: detached stray irq15 acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 And still get, # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Crist J. Clark wrote: I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 CRD-8400B/1.06 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? -- Crist J. Clark | [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: CDRW Stopped Working Moving to 6.x
On Thu, Sep 13, 2007 at 03:15:10PM -0700, Predrag Punosevac wrote: I know where is your problem the burning device is always cd0 Huh? Burncd(8) is explicitly for ATAPI CD-R/RW. From the man page, DESCRIPTION The burncd utility is used to burn CD-R/RW media using the ATAPI cd driver. All of the examples on the manpage use /dev/acd0. you must give the device node /dev/cd0 If I try it, # burncd -f /dev/cd0 -v -s 32 data hw.iso fixate burncd: ioctl(CDRIOCGETBLOCKSIZE): Device not configured Crist J. Clark wrote: On Thu, Sep 13, 2007 at 01:21:09PM -0700, Predrag Punosevac wrote: Make sure you add atapicam into your kernel it is not in generic! I had the same problem. /etc/loader.conf atapicam_load=YES I did a, # kldload /boot/kernel/atapicam.ko And to reinitiallize the drive, # atacontrol detach ata1 # atacontrol attach ata1 I got the same console message, acd0: detached (cd0:ata1:0:0:0): lost device (cd0:ata1:0:0:0): removing device entry atapicam1: detached stray irq15 acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 And still get, # burncd -f /dev/acd0 -t -s 32 data ~cjc/hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Crist J. Clark wrote: I just tried to burn a CD for the first time in a long time on a machine. The burncd(8) command worked fine on this machine in FreeBSD 5.x (or was it 4.x?), but now in 6.2, I get, # burncd -f /dev/acd0 -s 32 data hw.iso fixate burncd: ioctl(CDIOCSTART): Input/output error Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. I get this from atacontrol(8), # atacontrol info ata1 Master: acd0 CRD-8400B/1.06 ATA/ATAPI revision 0 Slave: no device present # atacontrol cap acd0 Protocol ATA/ATAPI revision 0 device model CRD-8400B serial number 1999/10/12 firmware revision 1.06 cylinders 0 heads 0 sectors/track 0 lba supported lba48 not supported dma supported overlap not supported Feature Support EnableValue Vendor write cacheno no read ahead no no Tagged Command Queuing (TCQ) no no 0/0x00 SMART no no microcode download no no security no no power management no no advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 How can I restore burning capability? -- Crist J. Clark | [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: CDRW Stopped Working Moving to 6.x
On Fri, Sep 14, 2007 at 07:35:24AM -0400, Lowell Gilbert wrote: Crist J. Clark [EMAIL PROTECTED] writes: Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. You're right, and that's the key point to start from. Don't worry about ATAPI/CAM; it won't be used by burncd, and won't work any better than direct ATAPI drivers if the device isn't recognized as a CDRW. The funny thing is (unless I recall incorrectly, which is possible before my first cup of coffee for the day), the ID string is provided by the device itself. And I just looked it up; CRD-8400B is definitely a CDROM. So I don't think the OS is confused; if anything, the device itself is what's confused. Just to doublecheck: are you really sure you haven't changed the drive since the last time you burned a CD? Nope, haven't changed the drive. Went and had a look at the front and it's got CD/RW on the disc symbol on the front of the tray. But going back to some old dmesg(1) from this same box when the buring worked back in 4.x, FreeBSD 4.11-STABLE #1: Sun Jun 19 00:18:37 PDT 2005 [EMAIL PROTECTED]:/var/tmp/tmp_cjc/obj/usr/src/sys/GOKU [snip] acd0: CDROM CRD-8400B at ata1-master PIO4 H... -- Crist J. Clark | [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: CDRW Stopped Working Moving to 6.x
On Wed, Sep 19, 2007 at 03:24:16PM -0400, Lowell Gilbert wrote: Crist J. Clark [EMAIL PROTECTED] writes: On Fri, Sep 14, 2007 at 07:35:24AM -0400, Lowell Gilbert wrote: Crist J. Clark [EMAIL PROTECTED] writes: Looking at the dmesg(1) from the last boot, # fgrep cd0 /var/run/dmesg.boot acd0: CDROM CRD-8400B/1.06 at ata1-master UDMA33 Makes me think the system is not recognizing the device as CDRW, only CDROM. You're right, and that's the key point to start from. Don't worry about ATAPI/CAM; it won't be used by burncd, and won't work any better than direct ATAPI drivers if the device isn't recognized as a CDRW. The funny thing is (unless I recall incorrectly, which is possible before my first cup of coffee for the day), the ID string is provided by the device itself. And I just looked it up; CRD-8400B is definitely a CDROM. So I don't think the OS is confused; if anything, the device itself is what's confused. Just to doublecheck: are you really sure you haven't changed the drive since the last time you burned a CD? Nope, haven't changed the drive. Went and had a look at the front and it's got CD/RW on the disc symbol on the front of the tray. But going back to some old dmesg(1) from this same box when the buring worked back in 4.x, FreeBSD 4.11-STABLE #1: Sun Jun 19 00:18:37 PDT 2005 [EMAIL PROTECTED]:/var/tmp/tmp_cjc/obj/usr/src/sys/GOKU [snip] acd0: CDROM CRD-8400B at ata1-master PIO4 H... Wow. Good thinking to check that. Definitely sounds like you are being bitten by something dodgy in the device probing which has been there for a long time but was benign in the past. You'll need someone who knows the probing code... S... After spending a few more hours trying to figure this out, I get some confusing messages when I just try to read a CDROM! Long story short, ha. ha. you'll laugh. I was looking at the wrong machine. The one with the drive clearly embosed with the disc symbol saying Rewritable is (besides also clearly being labeled with the system's name which is not the system I was trying to run the burncd(8) command on), acd0: CDRW Verbatim 522452AL/68S1 at ata1-master PIO4 And the machine I was trying to actually run the command on, the machine above, is indeed a CDROM. -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ppp(8) Over Dedicated Serial Link
Thought this would be easy. Probably is, but I'm missing something. I'm trying to get two FreeBSD boxes (5.5 and 6.2) to talk to each other over a dedicated serial link with ppp(8). This, to me, sounds exactly what direct and dedicated mode was designed for. On the PPP client I run, # ppp -dedicated hardwire In ppp.conf, hardwire: set log Phase Chat LCP IPCP IPV6CP CCP tun command set speed 115200 On the PPP server, I'm a little less confident. It sure sounds like direct mode is what I want. Since that doesn't connect to a device for me, I thought I'd use ttys(4) to do it, ttyd0 /usr/sbin/ppp -direct network on secure I don't think I want or need getty(8) since I'm not interested in doing logins on this link. It's an always up serial line between the hosts. But it's not working. What's the right way to do this? Do I actually need to go in and mess with the gettytab(4)? Why can't the ppp(8) just talk directly to the other end? -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Serial Console Problems
I've got DELL PowerEdge 1750 with 7.0-RELEASE-p4. I'm running the serial port to a serial console server. I thought I had the right adapter, DB-9 to RJ45, but it's being weird. When I specify, ttyd0 /usr/libexec/getty std.9600 vt100 on secure In the /etc/ttys file, the console doesn't work at all. However, when I do this, cuad0 /usr/libexec/getty std.9600 vt100 on secure It seems to work just fine. I think my adapter is close, but there is some signal being lost? Can anyone explain this one? I'm not sure I really understand the difference between a ttyd and cuad device from the paragraph in sio(4). Oh, and do I risk anything breaking by running my console off of a cuad? -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
interrupt storm detected
-0xd27ff pnpid ORM on isa0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio0: [FILTER] sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: [FILTER] Timecounter TSC frequency 499904191 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v4.1.28 initialized. Default = pass all, Logging = enabled ad0: 3847MB CF CARD 4GB 20071116 at ata0-master WDMA2 GEOM_LABEL: Label for provider ad0s1 is msdosfs/KINGSTON. Trying to mount root from nfs:goku:/home/net5501 NFS ROOT: 192.168.64.70:/home/net5501 -- Crist J. Clark | [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
