Re: XFCE based LiveDVD/IMG
I haven't tried from CD yet. Tim On Wed, Jul 25, 2012 at 12:01 PM, Sascha Wildner wrote: > On Wed, 25 Jul 2012 19:54:11 +0200, Tim Darby > wrote: > > Unfortunately, it failed during boot on my Dell Studio 14z laptop (1440), >> so I think DF just doesn't like this hardware. I did try booting without >> ACPI and AHCI, but no luck. Lots of errors, but where it failed each time >> was at device "xpt". I can provide exact error messages, if you want. >> > > Yeah, can't hurt. > > Does it fail with the regular CD/IMG too? > > Sascha >
Re: XFCE based LiveDVD/IMG
Yep, same here. Here are some of the messages I'm seeing: No /loader vm_page_alloc_contig: (a bunch of these) ahci0.0: START HARDRESET ahci0.0: Cannot start FIS reception ahci0.0: PMPROBE failed to start port, cannot soft reset ahci0.0: Cannot start FIS reception ahci0.0: failed to start command DMA on port, disabling ahci0.0: END HARDRESET 16 ahci0.0: waiting 10 seconds on insertion The above ahci sequence repeats about 4 times. fwohci0: phi read failed(1) (a ton of these) And eventually this: xpt: func=0x80281817 arg=0 (3 or 4 times) Giving up, interrupt routing is probably hosed Mounting root from ufs:da8s1a no disk named 'da8s1a' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Tim On Wed, Jul 25, 2012 at 12:23 PM, Pierre Abbat wrote: > On Wednesday 25 July 2012 13:54:11 Tim Darby wrote: > > Unfortunately, it failed during boot on my Dell Studio 14z laptop (1440), > > so I think DF just doesn't like this hardware. I did try booting without > > ACPI and AHCI, but no luck. Lots of errors, but where it failed each > time > > was at device "xpt". I can provide exact error messages, if you want. > > Sounds like my laptop. The interrupt routing is hosed and it couldn't mount > the root filesystem of the CD or thumb drive. > > Pierre > > -- > The Black Garden on the Mountain is not on the Black Mountain. >
Re: XFCE based LiveDVD/IMG
Unfortunately, it failed during boot on my Dell Studio 14z laptop (1440), so I think DF just doesn't like this hardware. I did try booting without ACPI and AHCI, but no luck. Lots of errors, but where it failed each time was at device "xpt". I can provide exact error messages, if you want. Tim On Mon, Jul 23, 2012 at 3:11 PM, Tim Darby wrote: > Thanks, I will definitely give this a try and let you know how it goes. > > Tim > > > > On Mon, Jul 23, 2012 at 3:01 PM, Sascha Wildner wrote: > >> Hi, >> >> I've been working on and off on a better, XFCE based DVD/IMG for some >> time (hehe, more off than on). >> >> The result of my attempts so far is here: >> >> http://island.quantumachine.**net/~swildner/LiveDVD/x86_64/<http://island.quantumachine.net/~swildner/LiveDVD/x86_64/> >> >> The USB image is larger than 4GB, unfortunately (I think around 5GB, as >> it was too full with 4GB). >> >> In addition to what we ship on our regular CD/IMG, it has the following >> packages installed: >> >> meta-pkgs/modular-xorg >> meta-pkgs/xfce4 >> meta-pkgs/xfce4-extras >> mail/thunderbird >> www/midori >> editors/emacs >> editors/vim >> misc/libreoffice >> multimedia/vlc >> chat/pidgin >> chat/irssi >> misc/tmux >> graphics/gimp >> graphics/xsane >> >> I have not yet verified how useful xsane is, or if it works at all. >> >> It might at least save some time for those who want to install or try out >> using these packages. >> >> Help, ideas, testing and comments are welcome. >> >> Sascha >> > >
Re: XFCE based LiveDVD/IMG
Thanks, I will definitely give this a try and let you know how it goes. Tim On Mon, Jul 23, 2012 at 3:01 PM, Sascha Wildner wrote: > Hi, > > I've been working on and off on a better, XFCE based DVD/IMG for some time > (hehe, more off than on). > > The result of my attempts so far is here: > > http://island.quantumachine.**net/~swildner/LiveDVD/x86_64/<http://island.quantumachine.net/~swildner/LiveDVD/x86_64/> > > The USB image is larger than 4GB, unfortunately (I think around 5GB, as it > was too full with 4GB). > > In addition to what we ship on our regular CD/IMG, it has the following > packages installed: > > meta-pkgs/modular-xorg > meta-pkgs/xfce4 > meta-pkgs/xfce4-extras > mail/thunderbird > www/midori > editors/emacs > editors/vim > misc/libreoffice > multimedia/vlc > chat/pidgin > chat/irssi > misc/tmux > graphics/gimp > graphics/xsane > > I have not yet verified how useful xsane is, or if it works at all. > > It might at least save some time for those who want to install or try out > using these packages. > > Help, ideas, testing and comments are welcome. > > Sascha >
Hammer log message
I saw this message in the log: HAMMER debug: shifted cursor pointing at parent parent 81992a0f:13 onode 819961415000:0 nnode 8199609b:50 I suspect this is just informational, but wanted to be sure. Tim
Re: Hammer mirroring question
Sure, df works fine. I was wondering if there was some status code or something thrown by hammer mirror-stream that would give me a more real time alert. Tim On Thu, Jun 21, 2012 at 8:11 AM, Tobias Weingartner wrote: > Does 'df' not work? > > -Toby. > > On Thu, Jun 21, 2012 at 8:57 AM, Tim Darby wrote: > > I really like that hammer mirror-stream resumes on its own after you > clear > > space on a destination drive that has filled up, but is there anything in > > hammer that can be used to alert you to a full slave drive? > > > > Tim >
Hammer mirroring question
I really like that hammer mirror-stream resumes on its own after you clear space on a destination drive that has filled up, but is there anything in hammer that can be used to alert you to a full slave drive? Tim
GPT question
Shouldn't gpt at a minimum check to see if a device is mounted before creating or destroying a table? I just lost a full 2TB drive's worth of data (backed up, fortunately) because I fat fingered the device name. Why would it ever be a good idea to allow this on a mounted device? Tim
Re: Hammer prune issue
Not totally sure but, during the prune, I can't make any new connections to the box and my SSH session gives up and I have to reconnect when the box is no longer busy. It's a 6 core AMD machine with 8GB of RAM running master, but it's not a new problem. Tim On Mon, Apr 30, 2012 at 5:52 PM, Justin Sherrill wrote: > On Mon, Apr 30, 2012 at 7:36 PM, Tim Darby wrote: > > When I run hammer prune-everything remotely via SSH, it pretty > consistently > > causes all network connections to that box to die, including my ssh > session. > > Has anyone else seen this? > > I have run prune-everything a bunch of times (since I manage to fill > disks regularly with bulk builds) and never saw this happen. > > Can you tell if it's actual drops or perhaps timeouts? If it's > timeouts, I'd wonder if it's some issue with heavy disk activity > keeping the system from responding as fast as it needs to. I'm > guessing, though. >
Hammer prune issue
When I run hammer prune-everything remotely via SSH, it pretty consistently causes all network connections to that box to die, including my ssh session. Has anyone else seen this? Tim
Re: Time problem
I thought this was a bug too and filed my own bug report on it, until it dawned on me that the intent of the installer is to set the system to UTC time instead of local time. In order to make this friendlier to new users, I suggest two questions in the installer: - Do you want UTC time or local time? - Is this machine's CMOS clock set to UTC? Tim On Thu, Apr 26, 2012 at 9:24 PM, Justin Sherrill wrote: > On Thu, Apr 26, 2012 at 11:41 PM, Donald Allen > wrote: > > I've installed Dragonfly 3.0.2 on an x86_64 box side-by-side with Arch > > Linux. Arch is set up for UTC time, America/New_York timezone. When I > > installed Dragonfly, I selected 'Yes' in response to the question "Is > > this machine's CMOS clock set to UTC?". Nonetheless, when Dragonfly > > came up, the time was 4 hours later than it should have been. After a > > bunch of detective work, I found that the presence of the file > > /etc/wall_cmos_clock indicates that the hardware clock is set to local > > time and that it was present. I removed it and the time became correct > > after a reboot. > > I bet the wall_cmos_clock file is present on the install CD and is > being copied over by cpdup independently. > > In any case, the long term answer (separate from fixing the > installer's behavior) is to set: > > dntpd_enable="YES" > > in rc.conf to make sure time remains accurate. >
Re: pkgsrc: multimedia/handbrake
On Tue, Jan 31, 2012 at 9:51 AM, John Marino wrote: > On 1/31/2012 4:48 PM, Tim Darby wrote: > > The build of handbrake fails as shown below. What do I need to do to get > > this working? > > > > A lot. You need to: > > bmake clean > > bmake patch > then go into the work directory and figure out why HB_NORMAL_PRIORITY > isn't defined. The normal cause of these things is that DragonFly isn't > recognized in the configuration or the cpp macros and header > includes/definitions don't get made. Sometimes the package is very > system-specific and just isn't supported by anything other than NetBSD. > You will be troubleshooting a broken package and this can take quite > some time. > > After you've identified the cause you can create a patch (or update an > existing patch if the file is question is already patched), and open a > PR with your patch. > > http://www.netbsd.org/support/send-pr.html > > If you fix it, tell me the PR number and I'll claim it and try to get > the fix into pkgsrc permanently. > > John > Thanks for the pointers. I'll dig into it and let you know. Tim
pkgsrc: multimedia/handbrake
The build of handbrake fails as shown below. What do I need to do to get this working? => Bootstrap dependency digest>=20010302: found digest-20080510 ===> Building for handbrake-0.9.3nb8 cd /usr/pkgsrc/multimedia/handbrake/work/HandBrake-0.9.3 && gmake gmake: svnversion: Command not found echo "#ifndef HB_BUILD" > libhb/hbversion.h echo "#define HB_BUILD 2012013101" >> libhb/hbversion.h echo "#endif" >> libhb/hbversion.h echo "#ifndef HB_VERSION" >> libhb/hbversion.h echo "#define HB_VERSION \"svn\"" >> libhb/hbversion.h echo "#endif" >> libhb/hbversion.h echo "#ifndef HB_APPCAST_URL" >> libhb/hbversion.h echo "#define APPCAST_URL \"http://handbrake.fr/appcast_unstable.xml\""; >> libhb/hbversion.h echo "#endif" >> libhb/hbversion.h gmake: Warning: File `libhb/hbversion.h' has modification time 0.0057 s in the future Cc hb.o echo cc -I../contrib/include -D__LIBHB__ -DUSE_PTHREAD -Wall -g -O3 -funroll-loops cc -I../contrib/include -D__LIBHB__ -DUSE_PTHREAD -Wall -g -O3 -funroll-loops hb.c: In function 'hb_init_real': hb.c:130: error: 'HB_NORMAL_PRIORITY' undeclared (first use in this function) hb.c:130: error: (Each undeclared identifier is reported only once hb.c:130: error: for each function it appears in.) hb.c: In function 'hb_init_dl': hb.c:206: error: 'HB_NORMAL_PRIORITY' undeclared (first use in this function) hb.c: In function 'hb_detect_comb': hb.c:456: warning: unused variable 'flag' Compile line for hb.o was: cc -I../contrib/include -D__LIBHB__ -DUSE_PTHREAD -Wall -g -O3 -funroll-loops -o hb.o -c hb.c gmake[1]: *** [hb.o] Error 1 gmake: *** [libhb/libhb.a] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/multimedia/handbrake *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/multimedia/handbrake Tim
Re: How to Correctly map sernos to device names
On Thu, Nov 24, 2011 at 3:14 AM, Siju George wrote: > Hi, > > Is there a way to correctly map /dev/serno to device names. > > Currently the devices I have are given below > > What is M00B3EK2306. Is it cd0? > > How does one know? > > Thanks > > --SIju > I'm not aware of an included utility to do this, but attached is a perl script I made, based on a perl script someone posted awhile ago, to convert serial numbers to devices. Tim sernotodev Description: Binary data
Re: SATA drive problem
Thanks, Francois. After some testing, I've determined that drive is definitely flaky and fortunately I'm still within the vendor return window. Tim On Wed, Jun 29, 2011 at 12:48 PM, Francois Tigeot wrote: > On Wed, Jun 29, 2011 at 10:22:24AM -0700, Tim Darby wrote: > > I tried to move a big folder from one SATA drive to another and the > machine > > stopped responding to the point that it lost network connectivity (DF > > 2.10.1). After reboot, I found the following errors: > [...] > > kernel: (da4:ahci0:4:0:0): READ(10). CDB: 28 0 80 3a d6 48 0 0 80 0 > > kernel: (da4:ahci0:4:0:0): CAM Status: SCSI Status Error > > kernel: (da4:ahci0:4:0:0): SCSI Status: Check Condition > > kernel: (da4:ahci0:4:0:0): MEDIUM ERROR asc:0,0 > [...] > > I'm guessing this is a drive problem, not a system problem, but just > wanted > > to check with the experts first. I haven't had a chance to run a drive > > diagnostic yet. I did try a repeat of that same mv command and it > happened > > again. The drive is just a month old, FWIW. > > I'll say some specific parts of the magnetic platters of your drive are > damaged and that's why you get this error every time trying to access the > same > files. > > A drive has not to be old to fail; failure during the first weeks of > activity > is relatively common. > It may have been badly packaged or handled during transport or may have > been > badly manufactured ... > > -- > Francois Tigeot >
SATA drive problem
I tried to move a big folder from one SATA drive to another and the machine stopped responding to the point that it lost network connectivity (DF 2.10.1). After reboot, I found the following errors: kernel: swap_pager: indefinite wait buffer: offset: 6631784448, size: 4096 kernel: swap_pager: indefinite wait buffer: offset: 6631800832, size: 4096 kernel: ahci0.4: TFES slot 28 ci_saved = 1f00 kernel: ahci0.4: read NCQ error page slot=8 kernel: ahci0.4: DONE log page target 0 err_slot=8 kernel: ahci0.4: disk_rw: error kernel: ahci0.4: Restart 1e00 kernel: (da4:ahci0:4:0:0): READ(10). CDB: 28 0 80 3a d6 48 0 0 80 0 kernel: (da4:ahci0:4:0:0): CAM Status: SCSI Status Error kernel: (da4:ahci0:4:0:0): SCSI Status: Check Condition kernel: (da4:ahci0:4:0:0): MEDIUM ERROR asc:0,0 kernel: (da4:ahci0:4:0:0): No additional sense information kernel: (da4:ahci0:4:0:0): Retrying Command (per Sense Data) kernel: ahci0.4: TFES slot 7 ci_saved = ffc000fd kernel: ahci0.4: read NCQ error page slot=22 kernel: ahci0.4: DONE log page target 0 err_slot=22 kernel: ahci0.4: disk_rw: error kernel: ahci0.4: Restart ff8000fd kernel: (da4:ahci0:4:0:0): READ(10). CDB: 28 0 80 3a dd 48 0 0 80 0 kernel: (da4:ahci0:4:0:0): CAM Status: SCSI Status Error kernel: (da4:ahci0:4:0:0): SCSI Status: Check Condition kernel: (da4:ahci0:4:0:0): MEDIUM ERROR asc:0,0 kernel: (da4:ahci0:4:0:0): No additional sense information kernel: (da4:ahci0:4:0:0): Retrying Command (per Sense Data) kernel: ahci0.4: TFES slot 8 ci_saved = ff800100 kernel: ahci0.4: read NCQ error page slot=8 kernel: ahci0.4: DONE log page target 0 err_slot=8 kernel: ahci0.4: disk_rw: error kernel: ahci0.4: Restart ff80 kernel: (da4:ahci0:4:0:0): READ(10). CDB: 28 0 80 3a dd 48 0 0 80 0 kernel: (da4:ahci0:4:0:0): CAM Status: SCSI Status Error kernel: (da4:ahci0:4:0:0): SCSI Status: Check Condition kernel: (da4:ahci0:4:0:0): MEDIUM ERROR asc:0,0 kernel: (da4:ahci0:4:0:0): No additional sense information kernel: (da4:ahci0:4:0:0): Retrying Command (per Sense Data) I'm guessing this is a drive problem, not a system problem, but just wanted to check with the experts first. I haven't had a chance to run a drive diagnostic yet. I did try a repeat of that same mv command and it happened again. The drive is just a month old, FWIW. Tim
Re: screen problem
Thanks. I installed it using pkg_radd and was hoping it would "just work". I haven't used screen before, so I couldn't rule out the possibility of PEBCAC. If I get a chance, I'll try compiling it to see if that makes a difference. Tim On Wed, Jun 15, 2011 at 7:44 AM, Matthias Rampke wrote: > > On Montag, 13. Juni 2011 at 22:21, Tim Darby wrote: > > > kernel: pid 18254 (screen-4.0.3), uid 0: exited on signal 11 (core > dumped) > I remember seeing that too. I don't exactly know what made it go away, > probably recompiling the package (and possibly some library it depends on) > from pkgsrc. > > hope that helps, > m. > > > >
screen problem
I get this in /var/log/messages when I try to run 'screen' in an ssh session on df 2.10.1: kernel: pid 18254 (screen-4.0.3), uid 0: exited on signal 11 (core dumped) I just wanted to let someone know in case this is a bug. I switched to dtach instead, which does what I need. Tim
Buffer strategy message?
I see this message on halt/reboot occasionally. Is it something I need to worry about? Synching disks... done No strategy for buffer at 0xffe056aabf00 : 0xffe0840876a8: type VBAD, sysrefs 1, writecount 0, holdcnt 0, Uptime: 12h9m53s the operating system has halted \ Tim
Re: PCI parallel port card
Thanks, Justin, I think this probably will work. I'll try it if I can't find a way to direct connect the printer. Tim On Sat, Apr 2, 2011 at 6:39 PM, Justin Sherrill wrote: > On Sat, Apr 2, 2011 at 6:33 PM, Tim Darby wrote: > > After playing with various device files, it's looking like this card is > just > > not going to work, at least not without more kernel skills than I have or > > possibly some imports from FreeBSD. So, let me ask a different question. > > What do you guys use to print to a parallel port printer when your > > motherboard doesn't have a built-in port? Can I solve this by using a > USB > > to parallel port converter? > > I've used RJ45 to parallel adapters (i.e. it makes a parallel port > printer into a network printer) at work, though not with DragonFly. > One of those may work the best because I _think_ it effectively lets > you print to the printer over the network using something simple like > lpr. Again, untested, but that's what I'd look for. >
Re: PCI parallel port card
After playing with various device files, it's looking like this card is just not going to work, at least not without more kernel skills than I have or possibly some imports from FreeBSD. So, let me ask a different question. What do you guys use to print to a parallel port printer when your motherboard doesn't have a built-in port? Can I solve this by using a USB to parallel port converter? Tim On Mon, Mar 21, 2011 at 3:52 PM, Tim Darby wrote: > I installed an I/O Future PP210 two parallel port PCI card and it's not > being recognized (DF 2.9.1 master). I get this in dmesg: > > pci4: (vendor 0x9710, dev 0x9865) at device > 6.0 irq 7 > pci4: (vendor 0x9710, dev 0x9865) at device > 6.2 irq 5 > > It's based on the NetMOS 9865 chip. I'm guessing I just need to make an > entry for it somewhere and rebuild the kernel (pcidev?). > > Here's the output of pciconf: > > none4@pci0:4:6:0: class=0x070103 card=0x2000a000 chip=0x98659710 rev=0x00 > hdr=0x00 > vendor = 'MosChip Semiconductors (Was: Netmos Technology)' > device = '?? PCI Serial Port X2' > class = simple comms > subclass = parallel port > none5@pci0:4:6:2: class=0x070103 card=0x2000a000 chip=0x98659710 rev=0x00 > hdr=0x00 > vendor = 'MosChip Semiconductors (Was: Netmos Technology)' > device = '?? PCI Serial Port X2' > class = simple comms > subclass = parallel port > > Tim >
PCI parallel port card
I installed an I/O Future PP210 two parallel port PCI card and it's not
being recognized (DF 2.9.1 master). I get this in dmesg:
pci4: (vendor 0x9710, dev 0x9865) at device
6.0 irq 7
pci4: (vendor 0x9710, dev 0x9865) at device
6.2 irq 5
It's based on the NetMOS 9865 chip. I'm guessing I just need to make an
entry for it somewhere and rebuild the kernel (pcidev?).
Here's the output of pciconf:
none4@pci0:4:6:0: class=0x070103 card=0x2000a000 chip=0x98659710 rev=0x00
hdr=0x00
vendor = 'MosChip Semiconductors (Was: Netmos Technology)'
device = '?? PCI Serial Port X2'
class = simple comms
subclass = parallel port
none5@pci0:4:6:2: class=0x070103 card=0x2000a000 chip=0x98659710 rev=0x00
hdr=0x00
vendor = 'MosChip Semiconductors (Was: Netmos Technology)'
device = '?? PCI Serial Port X2'
class = simple comms
subclass = parallel port
Tim
Re: Hammer recover question
Thanks, guys. Yes, I can see how it would slow down on the bad spots. I'm just happy it's working as well as it is and I'll try to be patient. Any way you can add a progress bar to this thing? :-) Tim On Sun, Feb 20, 2011 at 4:15 PM, Justin C. Sherrill < jus...@shiningsilence.com> wrote: > On Sun, February 20, 2011 4:28 pm, Tim Darby wrote: > > The good news is that it's recovering a ton of data! The > > bad news is that it's taking an incredible amount of time. So far it's > been > > running 24 hours. Is that to be expected? The bad disk had > approximately > > 50GB on it, as reported by the df utility, but I don't know how much of > > that is snapshots. > > I've had disks that go bad, and reading the raw data for recovery ends up > being very, very slow just when trying to read from the actual 'bad' > portions of disk. So this could take quite a while, just because of how > the physical disk is responding. > >
Hammer recover question
I have a very old server that I was pretty sure was going to fail sometime soon, so I prudently started building a new one. Unfortunately, I wasn't quite fast enough and the boot drive failed this week. When it tries to mount root, it issues the usual successful hammer startup messages and then quickly fails with: *READ_DMA status*=*51* *error*=*40* This was a 1.8.2 system. Having a 1.9 system handy, I plugged the drive (300GB IDE) into it and tried hammer recover for the first time to see what I could save. The good news is that it's recovering a ton of data! The bad news is that it's taking an incredible amount of time. So far it's been running 24 hours. Is that to be expected? The bad disk had approximately 50GB on it, as reported by the df utility, but I don't know how much of that is snapshots. Tim
Re: Random x86-64 seg-fault finally fixed
Here's hoping everyone has an MPSAFE New Year! And I'm hoping one of these 48-core monsters shows up under my Christmas tree. Tim On Wed, Dec 22, 2010 at 1:19 PM, Matthew Dillon wrote: > The random utility seg-fault (usually cc1) on x86-64 appears to have > finally been fixed. It turned out to be a vm_page race in the pageout > demon when it cycles pages onto the free page list. > > This clears the way for running the system with the remaining global > tokens set to MPSAFE mode. Test boxes are now running that way with no > errors so I expect we will be changing the tokens to run MPSAFE after > christmas sometime. We do still have to audit the code paths. > > I also expect to have a fine-grained VM solution at least for standard > VM faults by the next release, hopefully sooner. It appears to be the > biggest bottleneck on the monster 48-core test box now. > > Sascha has brought in the mps disk driver which is now undergoing > testing. This is the last big chipset support piece needed for 48-core > opteron supermicro support. The Gigabit ethernet uses the igb driver > which seems to work pretty well in polling mode. > >-Matt > Matthew Dillon > >
Re: Encrypted root questions
I've got more info on the messages I'm seeing below. I've determined that the initrd rc script is failing to kill udevd at the end when it is cleaning things up. It issues the kill command but udevd apparently never responds. This might explain why /tmp fails to unmount and also the seg-fault error. I tried editing the rc script to change "kill $UDEVD_PID" to "kill -9" and those messages went away. So what would cause udevd to not respond to SIGTERM? Tim On Sat, Dec 18, 2010 at 12:27 PM, Tim Darby > wrote: > Chris: agreed, email is not the best way to document things. I've > experienced that same frustration trying to track down some important detail > that only ever appeared in an email thread. > > That said, I have a few more questions. :) > > I now have encrypted root and encrypted swap set up (thanks, Alex) and I > was even able to make it read a keyfile for root on boot from a USB thumb > drive, although I found I had to add a mount command to the initrd rc file > to make that happen. So, happily, it boots all the way up without me having > to enter a passphrase. Referring to the snippet of dmesg below: > > - What are all these policies it keeps nagging about and should I care? > - Why does umount of /tmp fail? Is that a problem? > - What does the "seg-fault" line mean? > > Thanks, > > Tim > > Configuring LVM volumes > Reading all physical volumes. This may take a while... > Activated Volume Groups: > Mounting new root > WARNING!!! Possibly insecure memory, missing mlockall() > No policy for mapper/temporary-cryptsetup-160 specified, or policy not > found > disk scheduler: set policy of mapper/temporary-cryptsetup-16 to noop > No policy for mapper/temporary-cryptsetup-160 specified, or policy not > found > disk scheduler: set policy of mapper/temporary-cryptsetup-16 to noop > No policy for mapper/root0 specified, or policy not found > disk scheduler: set policy of mapper/root to noop > HAMMER(ROOT) recovery check seqno=002374c7 > HAMMER(ROOT) recovery range 326b5ad0-326b5ad0 > HAMMER(ROOT) recovery nexto 326b5ad0 endseqno=002374c8 > HAMMER(ROOT) mounted clean, no recovery needed > umount: > unmount of /tmp failed > : > Device busy > Mounting devfs on new root > chroot_kernel: set new rootnch/rootvnode to /new_root > /etc/rc: WARNING: $udevd_early is not set properly - see rc.conf(5). > Configuring crypto disks. > No policy for mapper/temporary-cryptsetup-431 specified, or policy not > found > seg-fault ft=0002 ff=000c addr=0 rip=0x401a90 pid=8 p_comm=udevd > disk scheduler: set policy of mapper/temporary-cryptsetup-43 to noop > Key slot 0 unlocked. > No policy for mapper/swap1 specified, or policy not found > disk scheduler: set policy of mapper/swap to noop > Loading configuration files. > Loading devfs rules: > /etc/defaults/devfs.conf > > > > On Mon, Dec 13, 2010 at 12:32 PM, Chris Turner < > c.tur...@199technologies.org> wrote: > >> Alex Hornung wrote: >> >>> For whatever it's worth, I've added a task to google code-in a few weeks >>> ago to document all this dm stuff, both cryptsetup and lvm, basically. >>> >> >> A bit OT but shouldn't this stuff go in bugs / the wiki and then be >> referenced to any "google code-in" or "foo barbaz-quux" to prevent >> fragmentation? >> >> (from someone who has had to do 'where did that note go' many a time :) >> >> cheers >> >> >> >> >> >> >> >
Re: Encrypted root questions
Chris: agreed, email is not the best way to document things. I've experienced that same frustration trying to track down some important detail that only ever appeared in an email thread. That said, I have a few more questions. :) I now have encrypted root and encrypted swap set up (thanks, Alex) and I was even able to make it read a keyfile for root on boot from a USB thumb drive, although I found I had to add a mount command to the initrd rc file to make that happen. So, happily, it boots all the way up without me having to enter a passphrase. Referring to the snippet of dmesg below: - What are all these policies it keeps nagging about and should I care? - Why does umount of /tmp fail? Is that a problem? - What does the "seg-fault" line mean? Thanks, Tim Configuring LVM volumes Reading all physical volumes. This may take a while... Activated Volume Groups: Mounting new root WARNING!!! Possibly insecure memory, missing mlockall() No policy for mapper/temporary-cryptsetup-160 specified, or policy not found disk scheduler: set policy of mapper/temporary-cryptsetup-16 to noop No policy for mapper/temporary-cryptsetup-160 specified, or policy not found disk scheduler: set policy of mapper/temporary-cryptsetup-16 to noop No policy for mapper/root0 specified, or policy not found disk scheduler: set policy of mapper/root to noop HAMMER(ROOT) recovery check seqno=002374c7 HAMMER(ROOT) recovery range 326b5ad0-326b5ad0 HAMMER(ROOT) recovery nexto 326b5ad0 endseqno=002374c8 HAMMER(ROOT) mounted clean, no recovery needed umount: unmount of /tmp failed : Device busy Mounting devfs on new root chroot_kernel: set new rootnch/rootvnode to /new_root /etc/rc: WARNING: $udevd_early is not set properly - see rc.conf(5). Configuring crypto disks. No policy for mapper/temporary-cryptsetup-431 specified, or policy not found seg-fault ft=0002 ff=000c addr=0 rip=0x401a90 pid=8 p_comm=udevd disk scheduler: set policy of mapper/temporary-cryptsetup-43 to noop Key slot 0 unlocked. No policy for mapper/swap1 specified, or policy not found disk scheduler: set policy of mapper/swap to noop Loading configuration files. Loading devfs rules: /etc/defaults/devfs.conf On Mon, Dec 13, 2010 at 12:32 PM, Chris Turner wrote: > Alex Hornung wrote: > >> For whatever it's worth, I've added a task to google code-in a few weeks >> ago to document all this dm stuff, both cryptsetup and lvm, basically. >> > > A bit OT but shouldn't this stuff go in bugs / the wiki and then be > referenced to any "google code-in" or "foo barbaz-quux" to prevent > fragmentation? > > (from someone who has had to do 'where did that note go' many a time :) > > cheers > > > > > > >
Re: Encrypted root questions
Thanks! Yes, I'm using master because I need it for the SATA ports on my
motherboard. I'd be willing to put up some documentation for this stuff,
but I don't want to snatch the google code-in opportunity away from some
deserving person. ;-)
Tim
On Mon, Dec 13, 2010 at 12:00 AM, Alex Hornung wrote:
> I'm assuming you are using the 'master' branch, otherwise the
> dm_target_crypt_load="YES" is not necessary. For whatever it's worth, I've
> added a task to google code-in a few weeks ago to document all this dm
> stuff, both cryptsetup and lvm, basically. Hopefully there will be a taker.
>
> For encrypted swap you definitely should be running the 'master' branch, as
> the release dm_target_crypt, while it supports it, would have problems under
> memory pressure. In any case: to set it up, you'd use the /etc/crypttab
> file; just add a line a la:
>
> swap/dev/da0s1bnonenone
>
> or, possibly, setting a keyfile, if that's what you'd like to use, as the
> third parameter. Man page should help you out on that. Then just add the
> following line to fstab:
>
> /dev/mapper/swapnoneswapsw10
>
> and you'll be all set up.
>
> Regards,
> Alex Hornung
>
>
> On 13/12/2010 06:24, Tim Darby wrote:
>
>> I'm trying to set up an encrypted root filesystem with disk A containing
>> /boot and swap and disk B containing the encrypted root. Having never done
>> this before, I figured I'd use /share/examples/rconfig/encrypted_root.sh as
>> a guide. However, I ran into a couple of snags, so maybe someone can tell
>> me what I'm doing wrong.
>>
>> First, this command appears to have a typo:
>>
>> cryptsetup -y luksFormat /dev/${disk}s1 <== shouldn't this be "s1d"?
>>
>> Second, in these lines for loader.conf:
>>
>>
>>
>> dm_load="YES"
>> initrd.img_load="YES"
>>
>>
>> initrd.img_type="md_image"
>> vfs.root.mountfrom="ufs:md0s0"
>>
>>
>> vfs.root.realroot="crypt:hammer:/dev/${disk}s1d:root"
>>
>>
>>
>> This failed for me during boot right after it prompted me for the
>> passphrase. Eventually, I realized that it was not able to find
>> dm_target_crypt.ko at the point where it was trying to open the encrypted
>> filesytem and I was only able to get the machine to successfully boot all
>> the way by adding the line:
>>
>> dm_target_crypt_load="YES"
>>
>> I'm also interested in encrypted swap. Is there anything tricky about
>> setting that up?
>>
>> Thanks,
>>
>> Tim
>>
>
>
Encrypted root questions
I'm trying to set up an encrypted root filesystem with disk A containing
/boot and swap and disk B containing the encrypted root. Having never done
this before, I figured I'd use /share/examples/rconfig/encrypted_root.sh as
a guide. However, I ran into a couple of snags, so maybe someone can tell
me what I'm doing wrong.
First, this command appears to have a typo:
cryptsetup -y luksFormat /dev/${disk}s1 <== shouldn't this be "s1d"?
Second, in these lines for loader.conf:
dm_load="YES"
initrd.img_load="YES"
initrd.img_type="md_image"
vfs.root.mountfrom="ufs:md0s0"
vfs.root.realroot="crypt:hammer:/dev/${disk}s1d:root"
This failed for me during boot right after it prompted me for the
passphrase. Eventually, I realized that it was not able to find
dm_target_crypt.ko at the point where it was trying to open the encrypted
filesytem and I was only able to get the machine to successfully boot all
the way by adding the line:
dm_target_crypt_load="YES"
I'm also interested in encrypted swap. Is there anything tricky about
setting that up?
Thanks,
Tim
Re: Horrible DF accident. Film at 11.
The recent snapshot works much better. :) Tim On Tue, Dec 7, 2010 at 6:51 PM, Matthew Dillon wrote: > :REINIT - Attempting to reinitialize the port after it had a horrible > :accident > : > :I had to chuckle over that. I mean, really, if you're going to have a > :message like that, you need to accompany it with sound effects. :) > : > :I'm guessing my mistake was to throw on 2.8.2 instead of a recent dev > :snapshot with the latest AHCI fixes. Does that sound right? I can, of > :course, provide a dmesg, if needed, but I'm not at the machine right now. > : > :Tim > > Yah :-). A recent master should do a better job with the AMD >AHCI chipset. > >-Matt >
Horrible DF accident. Film at 11.
So, I just installed DF on my shiny new GA-890GPA-UD3H equipped machine and, after some grumblings about PMProbes failing, I got this exciting error message: REINIT - Attempting to reinitialize the port after it had a horrible accident I had to chuckle over that. I mean, really, if you're going to have a message like that, you need to accompany it with sound effects. :) I'm guessing my mistake was to throw on 2.8.2 instead of a recent dev snapshot with the latest AHCI fixes. Does that sound right? I can, of course, provide a dmesg, if needed, but I'm not at the machine right now. Tim
Re: SSD for boot and swapcache
Cool and thanks for the tip about root chaining. I wasn't aware of that feature. Tim On Fri, Dec 3, 2010 at 12:26 PM, Matthew Dillon wrote: > > :I'm thinking of setting up a 40GB Intel SSD as both the boot drive and > :swapcache. Is this a reasonable thing to do? Are there any gotchas or > :things I need to watch out for as I set this up? I'd like to have /boot > as > :UFS and the rest of / as Hammer (the way the installer does it) and have / > :on a different drive. > : > :Tim > > Perfectly acceptable in my view. I would partition it 700MB for /boot, >1G reserved for an emergency root, and 32G for swap/swapcache. Leave > ~6G >unused at the end which you never write to ever (if this is a >fresh SSD). > >Another option, another reason why I suggest reserving 1G for an >emergency root, is that Alex has that root chaining feature in the >system now for dealing with encrypted root drives. The concept can >be used whether you encrypt your real root or not. You'd have to >play with it, but I recommend reserving that 1GB for potential future >use for things like that. > >The only real issue with SSD swap/swapcache has to do with excessive >normal paging to swap, which can eat up the SSDs life (i.e. not even >related to 'swapcache' itself, which is rate-limited). /boot itself >has virtually no impact on a SSD since it is only rarely written to. >Even installing a new kernel every few weeks would not have any impact. > >-Matt >
SSD for boot and swapcache
I'm thinking of setting up a 40GB Intel SSD as both the boot drive and swapcache. Is this a reasonable thing to do? Are there any gotchas or things I need to watch out for as I set this up? I'd like to have /boot as UFS and the rest of / as Hammer (the way the installer does it) and have / on a different drive. Tim
Re: Printer Daemon (Update)
I think I've always added myself to wheel too and just recently stopped doing that, so I can't say if printing as an unprivileged user ever worked in the past. Thanks again for the fix. Tim On Mon, Nov 29, 2010 at 7:18 PM, Joe Talbott wrote: > On Thu, Nov 25, 2010 at 09:35:23AM -0700, Tim Darby wrote: > > Success, thanks! Just a few comments: > > Great. I committed the patch. > > > > > - When I look at the commit history, it appears that the part you changed > > has been like that all the way back to the beginning of the project? > > I don't know if this issue has been here all along as I almost always > add myself to the wheel group. Do you know that this worked in the > past? If so, do you know what time frame. > > > - When I rebuilt kernel and world, I went ahead threw in all the recent > > MFC'ed things. Now, when I print to lpt0, I'm seeing these messages, > which > > I assume are harmless: > > > > Nov 25 08:58:34 ocotillo kernel: sched_ithd: stray interrupt 7 on cpu 0 > > Nov 25 08:58:34 ocotillo kernel: sched_ithd: stray interrupt 7 on cpu 0 > > Nov 25 08:58:34 ocotillo kernel: sched_ithd: 10 stray interrupts 7 on cpu > 0 > > - there will be no further reports > > I think you can ignore these if printing is working for you. > > Thanks, > Joe >
Re: Printer Daemon (Update)
Success, thanks! Just a few comments: - When I look at the commit history, it appears that the part you changed has been like that all the way back to the beginning of the project? - When I rebuilt kernel and world, I went ahead threw in all the recent MFC'ed things. Now, when I print to lpt0, I'm seeing these messages, which I assume are harmless: Nov 25 08:58:34 ocotillo kernel: sched_ithd: stray interrupt 7 on cpu 0 Nov 25 08:58:34 ocotillo kernel: sched_ithd: stray interrupt 7 on cpu 0 Nov 25 08:58:34 ocotillo kernel: sched_ithd: 10 stray interrupts 7 on cpu 0 - there will be no further reports - Just to satisfy my own curiosity about the code: how does lpr.c eventually get to unp_connect()? I followed it as far as connect() in startdaemon.c and then lost the trail. Thanks, Tim On Wed, Nov 24, 2010 at 9:04 AM, Joe Talbott wrote: > On Tue, Nov 23, 2010 at 09:57:06PM -0700, Tim Darby wrote: > > Here's the output: > > ~> ls -ld /var/run > > drwxr-xr-x 1 root wheel 0 Nov 21 23:14 /var/run > > ~> ls -ld /var > > drwxr-xr-x 1 root wheel 0 Aug 21 22:44 /var > > > > I agree; this is really bizarre-o. > > > > One other data point, fwiw: This machine, I'm pretty sure, started out > with > > a fresh install of DF 2.6, which was then upgraded via source to 2.8 and > > this is the first time I've used it to print. If I can find a spare > > machine, I'll try a fresh install. Would a vkernel make a good test? > > Please try the attached patch. There's a slight possibility of a > panic on boot so make a backup copy of /boot/kernel before > installkernel. > > Make sure to remove yourself from wheel if you added yourself and > logout and log back in before testing. > > Thanks, > Joe >
Re: Printer Daemon (Update)
Thanks, Joe. I'll try this later when I'm at the machine's location. Doesn't sound like a smart thing to try remotely. ;-) Tim On Wed, Nov 24, 2010 at 9:04 AM, Joe Talbott wrote: > On Tue, Nov 23, 2010 at 09:57:06PM -0700, Tim Darby wrote: > > Here's the output: > > ~> ls -ld /var/run > > drwxr-xr-x 1 root wheel 0 Nov 21 23:14 /var/run > > ~> ls -ld /var > > drwxr-xr-x 1 root wheel 0 Aug 21 22:44 /var > > > > I agree; this is really bizarre-o. > > > > One other data point, fwiw: This machine, I'm pretty sure, started out > with > > a fresh install of DF 2.6, which was then upgraded via source to 2.8 and > > this is the first time I've used it to print. If I can find a spare > > machine, I'll try a fresh install. Would a vkernel make a good test? > > Please try the attached patch. There's a slight possibility of a > panic on boot so make a backup copy of /boot/kernel before > installkernel. > > Make sure to remove yourself from wheel if you added yourself and > logout and log back in before testing. > > Thanks, > Joe >
Re: Printer Daemon (Update)
Here's the output: ~> ls -ld /var/run drwxr-xr-x 1 root wheel 0 Nov 21 23:14 /var/run ~> ls -ld /var drwxr-xr-x 1 root wheel 0 Aug 21 22:44 /var I agree; this is really bizarre-o. One other data point, fwiw: This machine, I'm pretty sure, started out with a fresh install of DF 2.6, which was then upgraded via source to 2.8 and this is the first time I've used it to print. If I can find a spare machine, I'll try a fresh install. Would a vkernel make a good test? Thanks, Tim On Tue, Nov 23, 2010 at 9:23 PM, Garance A Drosihn wrote: > On 11/22/10 9:41 PM, Tim Darby wrote: > > Here's the output: > > > > srwxrwx--- 1 root wheel 0 Nov 21 23:14 /var/run/printer > > uid=1001(tim) gid=1001(tim) groups=1001(tim) > > > > and this is the error I'm seeing: > > > >> /usr/bin/lpr -PHPLaser /home/tim/test > > lpr: Unable to connect to /var/run/printer: Permission denied > > lpr: Check to see if the master 'lpd' process is running. > > jobs queued, but cannot start daemon. > > > > What is the output from: ls -ld /var/run > And maybe: ls -ld /var > although I'd be pretty surprised if /var was the problem. > > Seems strange that several people are seeing this. I can't > imagine what's going on, so all I can do is make some wild > guesses at it. > > -- > Garance > g...@freebsd.org (lpr/lpd guy for FreeBSD) >
Re: Printer Daemon (Update)
Here's the output: srwxrwx--- 1 root wheel 0 Nov 21 23:14 /var/run/printer uid=1001(tim) gid=1001(tim) groups=1001(tim) and this is the error I'm seeing: > /usr/bin/lpr -PHPLaser /home/tim/test lpr: Unable to connect to /var/run/printer: Permission denied lpr: Check to see if the master 'lpd' process is running. jobs queued, but cannot start daemon. Note that the lpd daemon is definitely running, so that's not an issue. I think that error means that it can't fork the daemon to handle this job. Also, here's what I see in the spool dir: > ls -la /var/spool/output/lpd total 144 drwxr-xr-x 1 rootdaemon 0 Nov 21 23:17 . drwxr-xr-x 1 rootdaemon 0 Nov 21 22:52 .. -rw-rw---x 1 rootdaemon 4 Nov 21 23:17 .seq -rw-rw 1 daemon daemon 125 Nov 21 23:17 cfA204ocotillo.timdarby.com <http://cfa204ocotillo.timdarby.com/> -rw-rw 1 tim daemon 138992 Nov 21 23:17 dfA204ocotillo.timdarby.com <http://dfa204ocotillo.timdarby.com/> -rw-rw-r-- 1 rootdaemon 32 Nov 21 23:15 lock -rw-rw-r-- 1 rootdaemon 25 Nov 21 23:14 status That job will stay in the queue forever until I restart the queue or "bump" it by printing something as root. Thanks, Tim On Mon, Nov 22, 2010 at 6:56 PM, Joe Talbott wrote: > On Mon, Nov 22, 2010 at 03:50:18PM -0700, Tim Darby wrote: > > My /var/spool is a hammer pfs, as created by the installer defaults. > This > > feels like it has to be a permissions problem somewhere, but I haven't > had > > any luck finding it yet. > > What is the output of: > > ls -al /var/run/printer > id > > What are the exact error messages you are receiving? > > Thanks, > Joe >
Re: Printer Daemon (Update)
My /var/spool is a hammer pfs, as created by the installer defaults. This feels like it has to be a permissions problem somewhere, but I haven't had any luck finding it yet. Tim On Mon, Nov 22, 2010 at 3:32 PM, Chris Turner wrote: > Tim Darby wrote: > >> Anyone have any insights into this? >> > > What FS type is your /var/spool ? > > I seem to recall some kind of tmpfs permissions issues of late.. > > cheers >
Re: Printer Daemon (Update)
Yep, lpr looks right: -r-sr-sr-x 1 root daemon 26588 Nov 21 12:56 /usr/bin/lpr and I haven't put nosuid or nosgid on my filesystems. It's very puzzling. Tim On Sun, Nov 21, 2010 at 6:12 PM, Matthew Dillon wrote: >Hmm. > >apollo:/usr/src/sys/vfs/hammer> ls -la /usr/bin/lpr >-r-sr-sr-x 1 root daemon 26588 Oct 21 21:46 /usr/bin/lpr > >Make sure lpr is suid & sgid root:daemon. I am assuming your >filesystems aren't being mounted with the nosuid or nosgid mount >flags as well. > >If lpr can't access the socket it kinda sounds like it isn't running >sgid. > >-Matt >
Re: Printer Daemon (Update)
Oops, forgot to include printcap:
HPLaser|HPLaser:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh:mx#0:ff=
Tim
On Sun, Nov 21, 2010 at 4:03 PM, Tim Darby
> wrote:
> I'm seeing this exact problem on a 2.8.3 system. I've done the following
> troubleshooting steps:
>
> - Verified that I'm using the lpr that came with the system
> - Verified that my spool directory permissions are all correct
>
> When I print locally with lpr as root or as a user in the wheel group, it
> works fine. If I try to print as an unprivileged user, it fails. I noticed
> that changing permissions on the socket file /var/run/printer to 777 solves
> the problem, but that doesn't seem like a good answer. I see that lpr is
> suid and in lpr/common_source/startdaemon.c, before it tries to connect to
> the socket, it does a seteuid() to root, but I don't know what happens after
> that. Anyone have any insights into this?
>
> Tim
>
>
>
> On Sat, Mar 13, 2010 at 1:44 PM, Stephane Russell <
> sruss...@prodigeinfo.com> wrote:
>
>> I'm getting the same exact problem as described when printing from a
>> regular user:
>>
>> le...@alcyone: {102} lpq
>> alcyone: Warning: no daemon present
>> Rank Owner Job Files Total Size
>> 1stlette 618 (standard input) 697 bytes
>>
>> no entries
>>
>> I've just upgraded from 1.6 to 2.4, and I have this problem since. When
>> I'm printing from a user that is not in the 'wheel' group, I'm getting
>> this:
>>
>> le...@alcyone: {101} cat .cshrc | lp
>> lpr: Unable to connect to /var/run/printer: Permission denied
>> lpr: Check to see if the master 'lpd' process is running.
>> jobs queued, but cannot start daemon.
>>
>> I have a printer named impgal01, and my directories permissions are very
>> similar to the one you show:
>>
>> alcyone# ls -la /var/spool/lpd
>> total 4
>> drwxr-xr-x 2 root daemon 512 Dec 4 2007 .
>> drwxr-xr-x 17 root wheel 512 Jun 16 2008 ..
>>
>> alcyone# ls -lRa /var/spool/output
>> total 10
>> drwxr-xr-x 4 root daemon 512 Dec 5 2007 .
>> drwxr-xr-x 17 root wheel 512 Jun 16 2008 ..
>> drwxr-xr-x 2 root daemon 512 Mar 13 14:19 impgal01
>> drwxr-xr-x 2 root daemon 512 Mar 13 12:39 lpd
>> -rw-rw-r-- 1 root daemon4 Mar 13 15:25 lpd.lock
>>
>> /var/spool/output/impgal01:
>> total 10
>> drwxr-xr-x 2 root daemon 512 Mar 13 14:19 .
>> drwxr-xr-x 4 root daemon 512 Dec 5 2007 ..
>> -rw-rw---x 1 root daemon4 Mar 13 14:18 .seq
>> -rw-rw-r-- 1 root daemon 46 Mar 13 14:01 lock
>> -rw-rw-r-- 1 root daemon 18 Mar 13 14:01 status
>>
>> /var/spool/output/lpd:
>> total 4
>> drwxr-xr-x 2 root daemon 512 Mar 13 12:39 .
>> drwxr-xr-x 4 root daemon 512 Dec 5 2007 ..
>>
>> It really seems that something changed in lpd between 1.6 and 2.4. I'll
>> have no choice than to chmod /var/run/printer if I want users to print.
>>
>> SR
>>
>>
>> Matthew Dillon a écrit :
>> > :Update
>> > :
>> > :The socket /var/run/printer has permissions rwxrwx---. If I change them
>> > :to rwxrwxrwx there is no problem printing.
>> > :
>> > :Since no one else is complaining about this I assume I have something
>> > :set incorrectly but have run out of ideas.
>> > :
>> > :Thanks, Jim Chapman
>> >
>> > Hmm. On my printer box that socket is 770 and I can print fine so
>> > I think changing the perms might just be masking the issue you are
>> > having.
>> >
>> > Usually printer daemon problems are due to ownership/group issues
>> > in /var/spool/lpd or /var/spool/output, or path specifications
>> > that are not accessible by group 'daemon'.
>> >
>> > backup# ls -la /var/spool/lpd
>> > total 2
>> > drwxr-xr-x 2 root daemon 512 Sep 12 2005 .
>> > drwxr-xr-x 11 root wheel 512 Apr 2 2008 ..
>> >
>> > backup# ls -lRa /var/spool/output
>> > total 4
>> > drwxr-xr-x 3 root daemon 512 Sep 22 10:57 .
>> > drwxr-xr-x 11 root wheel 512 Apr 2 2008 ..
>> > drwxr-xr-x 2 root daemon 512 Dec 1 10:23 lpd
>> > -rw-rw-r-- 1 root daemon4 Dec 4 21:53 lpd.lock
>> >
>> > /var/spool/output/lpd:
>> > total 5
>> > drwxr-xr-x 2 root daemon 512 Dec 1 10:23 .
>> > drwxr-xr-x 3 root daemon 512 Sep 22 10:57 ..
>> > -rw-rx 1 root daemon4 Sep 22 11:04 .seq
>> > -rw-rw-r-- 1 root daemon 33 Dec 1 10:23 lock
>> > -rw-rw-r-- 1 root daemon 25 Dec 1 10:23 status
>> > backup#
>> >
>> > In particular the lock file in /var/spool/output has to be 664
>> > and the lock and status files in /var/spool/output/lpd have to be
>> > 664. And the group has to be 'daemon'.
>> >
>> > -Matt
>> > Matthew Dillon
>> >
>>
>
>
Re: Printer Daemon (Update)
I'm seeing this exact problem on a 2.8.3 system. I've done the following
troubleshooting steps:
- Verified that I'm using the lpr that came with the system
- Verified that my spool directory permissions are all correct
When I print locally with lpr as root or as a user in the wheel group, it
works fine. If I try to print as an unprivileged user, it fails. I noticed
that changing permissions on the socket file /var/run/printer to 777 solves
the problem, but that doesn't seem like a good answer. I see that lpr is
suid and in lpr/common_source/startdaemon.c, before it tries to connect to
the socket, it does a seteuid() to root, but I don't know what happens after
that. Anyone have any insights into this?
Tim
On Sat, Mar 13, 2010 at 1:44 PM, Stephane Russell
wrote:
> I'm getting the same exact problem as described when printing from a
> regular user:
>
> le...@alcyone: {102} lpq
> alcyone: Warning: no daemon present
> Rank Owner Job Files Total Size
> 1stlette 618 (standard input) 697 bytes
>
> no entries
>
> I've just upgraded from 1.6 to 2.4, and I have this problem since. When
> I'm printing from a user that is not in the 'wheel' group, I'm getting
> this:
>
> le...@alcyone: {101} cat .cshrc | lp
> lpr: Unable to connect to /var/run/printer: Permission denied
> lpr: Check to see if the master 'lpd' process is running.
> jobs queued, but cannot start daemon.
>
> I have a printer named impgal01, and my directories permissions are very
> similar to the one you show:
>
> alcyone# ls -la /var/spool/lpd
> total 4
> drwxr-xr-x 2 root daemon 512 Dec 4 2007 .
> drwxr-xr-x 17 root wheel 512 Jun 16 2008 ..
>
> alcyone# ls -lRa /var/spool/output
> total 10
> drwxr-xr-x 4 root daemon 512 Dec 5 2007 .
> drwxr-xr-x 17 root wheel 512 Jun 16 2008 ..
> drwxr-xr-x 2 root daemon 512 Mar 13 14:19 impgal01
> drwxr-xr-x 2 root daemon 512 Mar 13 12:39 lpd
> -rw-rw-r-- 1 root daemon4 Mar 13 15:25 lpd.lock
>
> /var/spool/output/impgal01:
> total 10
> drwxr-xr-x 2 root daemon 512 Mar 13 14:19 .
> drwxr-xr-x 4 root daemon 512 Dec 5 2007 ..
> -rw-rw---x 1 root daemon4 Mar 13 14:18 .seq
> -rw-rw-r-- 1 root daemon 46 Mar 13 14:01 lock
> -rw-rw-r-- 1 root daemon 18 Mar 13 14:01 status
>
> /var/spool/output/lpd:
> total 4
> drwxr-xr-x 2 root daemon 512 Mar 13 12:39 .
> drwxr-xr-x 4 root daemon 512 Dec 5 2007 ..
>
> It really seems that something changed in lpd between 1.6 and 2.4. I'll
> have no choice than to chmod /var/run/printer if I want users to print.
>
> SR
>
>
> Matthew Dillon a écrit :
> > :Update
> > :
> > :The socket /var/run/printer has permissions rwxrwx---. If I change them
> > :to rwxrwxrwx there is no problem printing.
> > :
> > :Since no one else is complaining about this I assume I have something
> > :set incorrectly but have run out of ideas.
> > :
> > :Thanks, Jim Chapman
> >
> > Hmm. On my printer box that socket is 770 and I can print fine so
> > I think changing the perms might just be masking the issue you are
> > having.
> >
> > Usually printer daemon problems are due to ownership/group issues
> > in /var/spool/lpd or /var/spool/output, or path specifications
> > that are not accessible by group 'daemon'.
> >
> > backup# ls -la /var/spool/lpd
> > total 2
> > drwxr-xr-x 2 root daemon 512 Sep 12 2005 .
> > drwxr-xr-x 11 root wheel 512 Apr 2 2008 ..
> >
> > backup# ls -lRa /var/spool/output
> > total 4
> > drwxr-xr-x 3 root daemon 512 Sep 22 10:57 .
> > drwxr-xr-x 11 root wheel 512 Apr 2 2008 ..
> > drwxr-xr-x 2 root daemon 512 Dec 1 10:23 lpd
> > -rw-rw-r-- 1 root daemon4 Dec 4 21:53 lpd.lock
> >
> > /var/spool/output/lpd:
> > total 5
> > drwxr-xr-x 2 root daemon 512 Dec 1 10:23 .
> > drwxr-xr-x 3 root daemon 512 Sep 22 10:57 ..
> > -rw-rx 1 root daemon4 Sep 22 11:04 .seq
> > -rw-rw-r-- 1 root daemon 33 Dec 1 10:23 lock
> > -rw-rw-r-- 1 root daemon 25 Dec 1 10:23 status
> > backup#
> >
> > In particular the lock file in /var/spool/output has to be 664
> > and the lock and status files in /var/spool/output/lpd have to be
> > 664. And the group has to be 'daemon'.
> >
> > -Matt
> > Matthew Dillon
> >
>
Re: Native jdk15 build
Thanks, I'd like to try this. Tim On Sun, Nov 14, 2010 at 9:10 AM, Francois Tigeot wrote: > Hi all! > > I have just succeeded in building a native jdk: > > $ /usr/pkg/java/jdk-1.5.0/bin/java -version > java version "1.5.0_16-p9" > Java(TM) 2 Runtime Environment, Standard Edition (build > 1.5.0_16-p9-ftigeot_14_nov_2010_14_56) > Java HotSpot(TM) 64-Bit Server VM (build > 1.5.0_16-p9-ftigeot_14_nov_2010_14_45, mixed mode) > > My work is based on the old jdk15 pkgsrc-wip entry, which has unfortunately > been recently deleted. > > I'll ask the pkgsrc guys if it can be revived. > > Is there any preferred way to publish patches if this can not be done ? In > the > worst case, I may setup a web page... > > -- > Francois Tigeot >
Re: Linuxulator question, boot loader oddity
I'm willing to go with that explanation, lacking a better one. ;-) However, in vi I would have had to accidentally type the sequence g~~, which doesn't seem likely. Tim On Sun, Nov 7, 2010 at 1:45 PM, Justin C. Sherrill wrote: > On Sun, November 7, 2010 8:45 am, Tim Darby wrote: >> That's when I noticed that loader.conf looked like >> this: >> >> VFS.ROOT.MOUNTFROM="HAMMER:SERNO/s0a4j1ta141435.S1D" >> linux_load=yes >> >> I tried changing the mountfrom line to: >> vfs.root.mountfrom="hammer:serno/S0A4J1TA141435.s1d" > > I don't know what editor you use, but is it possible you somehow hit the > right key sequence to invert case on that line while entering the > linuxulator stuff? It's a guess, but it fits the symptoms. > >
Linuxulator question, boot loader oddity
I'm running 2.8 now and it looks great so far. I setup linuxulator for the first time yesterday as follows: - added linux_load=yes to /boot/loader.conf - added linux_enable=yes to /etc/rc.conf - pkg_radd suse_base - mount -t linprocfs none /usr/pkg/emul/linux/proc Did I miss anything? I've only tested it with java and that works fine. Here's the weird part. After I added the line linux_load=yes to /boot/loader.conf, the machine failed to come up and landed me at the mountroot prompt. That's when I noticed that loader.conf looked like this: VFS.ROOT.MOUNTFROM="HAMMER:SERNO/s0a4j1ta141435.S1D" linux_load=yes I tried changing the mountfrom line to: vfs.root.mountfrom="hammer:serno/S0A4J1TA141435.s1d" This fixed the root mount. So, I'm wondering how my system was able to boot before I made this change and why did simply adding a line to loader.conf cause it to break? Tim
Re: Intel CPU question
Thanks everyone, looks like it's AMD for me. Tim On Tue, Oct 12, 2010 at 8:41 AM, Matthew Dillon wrote: > :On Tue, Oct 12, 2010 at 12:09:51AM +0200, Antonio Huete Jimenez wrote: > :> > :> I recently bought a Phenom X6 1055T in a Gigabyte 880GA-UD3H > :> motherboard, and besides ACPI, everything I've used _seems_ to work > :> fine. I haven't done much testing yet though. > :> For example, I have NOT tested the audio card or run Xorg on it :) > :> > :> 2010/10/11 Tim Darby >: > :> > Does DragonFly support Core I7 or is AMD a safer choice? I'm ready to > build > :> > a high end multi-core box and was wondering what my options are. > :> > Known-to-work motherboard suggestions would also be greatly > appreciated. > : > :AMD is a safer bet, there's too much complexity on the Intel side > nowadays. > : > :This Gigabyte board is a good choice; you should try to get an AMD880 > chipset > :based board, everything just works including Xorg. > : > :-- > :Francois Tigeot > > I'm pretty happy with the gigabyte board. There are still some issues >with AHCI but mostly pertaining to host-swap and external enclosures. >All I feel are fixable even if I have to depart from the AHCI spec >a bit as a special case. > >-Matt > Matthew Dillon > >
Intel CPU question
Does DragonFly support Core I7 or is AMD a safer choice? I'm ready to build a high end multi-core box and was wondering what my options are. Known-to-work motherboard suggestions would also be greatly appreciated. :-) Thanks, Tim
Linuxulator question
What's the status of the Linuxulator? I saw that Alex put a lot of work into it, so is it basically done and just needs testers? Thanks, Tim
Re: Why did you choose DragonFly?
I got interested in DragonFly early on because of the stated goals. It was exciting to see a BSD project that was really trying to advance the kernel. I started replacing more and more of my machines with DF until I had only one holdout, an OpenBSD machine for pf, and then that one got replaced too when the DragonFly's pf implementation improved. I can't say enough about how awesome HAMMER is and vkernel too. I also very much appreciate the people here. For the most part, you guys are light years beyond me in UNIX knowledge, yet you take the trouble to share that knowledge. I learn a lot just following the mailing lists. Are you going to throw a party when the BGL is completely gone? I'll bring the beer. :-) Tim On Mon, Sep 20, 2010 at 12:33 PM, Samuel J. Greear wrote: > This mail is intended for the infrequent responders and lurkers on the > list just as much as the regular posters. > > What has drawn you to use the DragonFly BSD operating system and/or > participate in its development by following this list? Technical > features, methodologies, something about the community? I suspect the > HAMMER filesystem to be the popular choice, but what other features > affect or do you see affecting your day to day life as an > administrator, developer, or [insert use case here], now or in the > future? > > Thanks in advance for your response. > > Best, > Sam >
MPSAFE work
I'm noticing a lot of MPSAFE work in this dev cycle. Does this mean I'll see the end of the BGL in my lifetime? :-) Tim
Hammer inode warnings
I'm guessing this behavior is OK but just wanted to be sure. I was playing around with the undo utility and tried: ocotillo# undo -i /data2/* Warning: fake transaction id 0x000100018040 Warning: fake transaction id 0x000100136040 /data2/tim: ITERATE ENTIRE HISTORY 0x000100696e80 13-Feb-2010 22:19:36 0x000102c2fc70 22-Feb-2010 01:00:25 0x000103075fe0 17-Mar-2010 01:00:04 0x000103698380 16-Apr-2010 01:00:24 Warning: fake transaction id 0x000100018040 /data2/video: ITERATE ENTIRE HISTORY 0x000100093f00 09-Feb-2010 18:50:57 file-deleted 0x0001000c9710 10-Feb-2010 18:49:37 0x0001000d1f20 10-Feb-2010 18:53:26 0x00010011f9d0 10-Feb-2010 19:39:14 0x000102bf39e0 15-Feb-2010 18:47:10 0x000102bfc7e0 16-Feb-2010 10:29:31 0x000102c23c50 20-Feb-2010 10:59:04 0x000102c2cb30 21-Feb-2010 09:48:22 0x000102c2cb90 21-Feb-2010 09:49:24 0x000102c2cbd0 21-Feb-2010 09:49:55 0x000102c2cc50 21-Feb-2010 09:50:26 0x000102c2ccb0 21-Feb-2010 09:50:57 0x000102c2cd10 21-Feb-2010 09:51:28 0x000102c2cdb0 21-Feb-2010 09:52:30 0x000102c2cdf0 21-Feb-2010 09:53:01 0x000102c2ce50 21-Feb-2010 09:53:32 0x000102c2d050 21-Feb-2010 10:00:15 0x000102c2d130 21-Feb-2010 10:02:19 0x000102c2d270 21-Feb-2010 10:15:45 0x000102c2d3d0 21-Feb-2010 10:21:26 0x000102c2d510 21-Feb-2010 10:26:05 0x000102c2d730 21-Feb-2010 10:32:48 0x000102c2d810 21-Feb-2010 10:34:21 0x000102c2d9d0 21-Feb-2010 10:41:04 0x000102c355b0 22-Feb-2010 18:09:25 0x000102cf1530 26-Feb-2010 17:39:18 0x000102d2b070 27-Feb-2010 22:32:19 0x000102d57950 28-Feb-2010 20:01:36 0x000102d8efd0 01-Mar-2010 23:03:04 0x000102fd5040 13-Mar-2010 10:30:07 0x0001031b9520 23-Mar-2010 18:11:00 0x00010343f860 10-Apr-2010 15:12:23 0x0001035e1c60 13-Apr-2010 19:52:36 0x0001035eb090 13-Apr-2010 22:19:04 0x0001036332f0 15-Apr-2010 18:19:53 0x000103663450 15-Apr-2010 18:20:54 0x000103663470 15-Apr-2010 18:20:54 0x000104fc9a10 20-Apr-2010 17:55:21 0x0001050f38f0 25-Apr-2010 18:09:54 0x000105134150 26-Apr-2010 16:14:53 0x00010513b490 26-Apr-2010 19:45:57 0x00010514ea30 26-Apr-2010 21:17:55 0x0001051ebbe0 28-Apr-2010 18:01:47 What's worrisome is the messages this generated in /var/messages: May 4 17:10:12 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "tim@@0x000100136040" May 4 17:10:12 ocotillo kernel: obj_id = 0001000aed5c, asof=000100136040, lo= May 4 17:10:12 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "tim@@0x000100136040" May 4 17:10:12 ocotillo kernel: obj_id = 0001000aed5c, asof=000100136040, lo= May 4 17:10:12 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "tim@@0x000100136040" May 4 17:10:12 ocotillo kernel: obj_id = 0001000aed5c, asof=000100136040, lo= May 4 17:10:12 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "tim@@0x000100136040" May 4 17:10:12 ocotillo kernel: obj_id = 0001000aed5c, asof=000100136040, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "tim@@0x000100136040" May 4 17:17:13 ocotillo kernel: obj_id = 0001000aed5c, asof=000100136040, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "tim@@0x000100136040" May 4 17:17:13 ocotillo kernel: obj_id = 0001000aed5c, asof=000100136040, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "video@@0x000100018040" May 4 17:17:13 ocotillo kernel: obj_id = 000107e6, asof=000100018040, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "video@@0x000100018040" May 4 17:17:13 ocotillo kernel: obj_id = 000107e6, asof=000100018040, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "video@@0x000100029900" May 4 17:17:13 ocotillo kernel: obj_id = 000107e6, asof=000100029900, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "video@@0x000100029900" May 4 17:17:13 ocotillo kernel: obj_id = 000107e6, asof=000100029900, lo= May 4 17:17:13 ocotillo kernel: HAMMER: WARNING: Missing inode for dirent "video@@0x000100031ad0" May 4 17:17:13 ocotillo kernel: obj_id = 000107e6, asof=000100031ad0, lo= May 4 17:17:1
Re: SiI 3124 support
On Sat, Jan 30, 2010 at 11:35 AM, Matthew Dillon <
dil...@apollo.backplane.com> wrote:
>
> :Cool, it "just works". I tried it today using a Rosewill RC-217 4-port
> SATA
> :PCI card. I was able to create a Hammer volume and copy files to it.
> : Attached is the dmesg:
> :
> :Thanks,
> :Tim
>
> Heh. Actually it didn't quite work. The ATA driver picked it up.
>The ATA driver does have support for the 3124 but it isn't as advanced
>as the SILI driver. You won't get hotswap or NCQ, for example. If
>you want to experiment please try adding the PCI ID entry to the SILI
>driver and see if it can probe it. If it can it will take precedence
>over the ATA probe of the same device.
>
>-Matt
>
>
Ok, does this look better? :-) The entry I added is:
.ad_vendor = PCI_VENDOR_SII,
.ad_product = 0x3124,
.ad_nports = 4,
.ad_attach = sili_pci_attach,
.ad_detach = sili_pci_detach,
.name = "Rosewill-3124-SATA"
Tim
Copyright (c) 2003-2009 The DragonFly Project.
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
DragonFly v2.4.1.40.ga038d-RELEASE #0: Sat Jan 30 14:55:29 MST 2010
r...@ocotillo.timdarby.com:/usr/obj/usr/src/sys/MYKERNEL
TSC clock: 1794110512 Hz, i8254 clock: 1193137 Hz
CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.19-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf24 Stepping = 4
Features=0x3febfbff
real memory = 804519936 (785664K bytes)
avail memory = 766943232 (748968K bytes)
kbd1 at kbdmux0
Pentium Pro MTRR support enabled
fildesc_drvinit() building stdin, stdout, stderr:
md0: Malloc disk
ACPI: RSDP 0xf6cc0 00014 (v0 ACPIAM)
ACPI: RSDT 0x2ff4 0002C (v1 A M I OEMRSDT 09000210 MSFT 0097)
ACPI: FACP 0x2ff40200 00081 (v2 A M I OEMFACP 09000210 MSFT 0097)
ACPI: DSDT 0x2ff40400 039D5 (v1 DELL DIM 4500 010A MSFT 010D)
ACPI: FACS 0x2ff5 00040
ACPI: APIC 0x2ff40300 00054 (v1 A M I OEMAPIC 09000210 MSFT 0097)
npx0: on motherboard
npx0: INT 16 interface
Using XMM optimized bcopy/copyin/copyout
acpi0: on motherboard
acpi0: Power Button (fixed)
Warning: ACPI is disabling APM's device. You can't run both
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0: on acpi0
cpu_cst0: on cpu0
acpi_button0: on acpi0
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
ppc0 port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0: on ppc0
plip0: on ppbus0
lpt0: on ppbus0
lpt0: Interrupt-driven port
ppi0: on ppbus0
atkbdc0: port 0x64,0x60 irq 1 on acpi0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
pcib0: pcibus 0 on motherboard
pir0: on motherboard
pci0: on pcib0
agp0: mem 0xf800-0xfbff at device
0.0 on pci0
pcib1: at device 1.0 on pci0
pci1: on pcib1
vgapci0: port 0xc800-0xc8ff mem
0xff7fc000-0xff7f,0xf000-0xf3ff irq 11 at device 0.0 on pci1
uhci0: port 0xe800-0xe81f irq 11
at device 29.0 on pci0
usb0: on uhci0
usb0: USB revision 1.0
uhub0: on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: port 0xe880-0xe89f irq 3
at device 29.1 on pci0
usb1: on uhci1
usb1: USB revision 1.0
uhub1: on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: port 0xec00-0xec1f irq 5
at device 29.2 on pci0
usb2: on uhci2
usb2: USB revision 1.0
uhub2: on usb2
uhub2: 2 ports with 2 removable, self powered
pci0: (vendor 0x8086, dev 0x24cd) at device 29.7 irq 9
pcib2: at device 30.0 on pci0
pci2: on pcib2
sili0: port 0xdc00-0xdc0f mem
0xff9f-0xff9f7fff,0xff9ffc00-0xff9ffc7f irq 10 at device 1.0 on pci2
sili0: ports=4 tags=31, cap=NCQ,FBSS,SPM
sili0.0.15: PM softreset
sili0.0: reiniting port after error reent=0 expired=
sili0.0.15: PM softreset done error 5
sili0.0: Found DISK "SAMSUNG SP2004C VM100-33" serial="S07GJ10Y523211"
sili0.0: tags=32/31 satacap=0706 satafea=004c NCQ=YES capacity=190782.21MB
sili0.0: f85=7469 f86=3c01 f87=4023 WC=enabled RA=enabled SEC=freezing
sili0.1: No device detected
sili0.2: No device detected
sili0.3: No device detected
em0: port 0xd880-0xd8bf
mem 0xff9a-0xff9b,0xff9c-0xff9d irq 11 at device 12.0 on
pci2
em0: MAC address: 00:07:e9:0a:5a:1f
isab0: at device 31.0 on pci0
isa0: on isab0
atapci0: port
0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0
ata0: on atapci0
ad0: 38166MB at ata0-master UDMA100
ata1: on atapci0
acd0: DVDROM at ata1-master UDMA33
pci0: (vendor 0x8086, dev 0x24c3) at device 31.3 irq 11
pci0: (vendor
Re: SiI 3124 support
On Sat, Jan 30, 2010 at 11:35 AM, Matthew Dillon < dil...@apollo.backplane.com> wrote: > > :Cool, it "just works". I tried it today using a Rosewill RC-217 4-port > SATA > :PCI card. I was able to create a Hammer volume and copy files to it. > : Attached is the dmesg: > : > :Thanks, > :Tim > > Heh. Actually it didn't quite work. The ATA driver picked it up. >The ATA driver does have support for the 3124 but it isn't as advanced >as the SILI driver. You won't get hotswap or NCQ, for example. If >you want to experiment please try adding the PCI ID entry to the SILI >driver and see if it can probe it. If it can it will take precedence >over the ATA probe of the same device. > > -Matt > > Oops, I see that now. ;-) I'll try test you suggested. Tim
Re: SiI 3124 support
On Mon, Jan 25, 2010 at 3:53 PM, Matthew Dillon wrote: > :How good is the Silicon Image 3124 chipset support in the sili(4) driver? > :Has it been well tested? > : > :Thanks, > :Tim > > I don't have a 3124 board or a machine with PCI-X slots to test with. >I believe the 3124 chipset spec is very similar to the 3132 spec which >means it should be easy to add support for the 3124 in our sili driver. > >Someone with a board and a slot is needed to do it. It might even >be possible that the only addition required is the PCI ID for the 3124 >in the sili_devices[] array in /usr/src/sys/dev/disk/sili/sili_attach.c. > >-Matt >Matthew Dillon > > Cool, it "just works". I tried it today using a Rosewill RC-217 4-port SATA PCI card. I was able to create a Hammer volume and copy files to it. Attached is the dmesg: Thanks, Tim Copyright (c) 2003-2009 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly v2.4.1-RELEASE #14: Wed Sep 30 18:12:31 PDT 2009 r...@test28.backplane.com:/usr/obj/usr/src-misc/sys/GENERIC TSC clock: 1794108240 Hz, i8254 clock: 1193136 Hz CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1794.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 804519936 (785664K bytes) avail memory = 766943232 (748968K bytes) kbd1 at kbdmux0 Pentium Pro MTRR support enabled fildesc_drvinit() building stdin, stdout, stderr: md0: Malloc disk ACPI: RSDP 0xf6cc0 00014 (v0 ACPIAM) ACPI: RSDT 0x2ff4 0002C (v1 A M I OEMRSDT 09000210 MSFT 0097) ACPI: FACP 0x2ff40200 00081 (v2 A M I OEMFACP 09000210 MSFT 0097) ACPI: DSDT 0x2ff40400 039D5 (v1 DELL DIM 4500 010A MSFT 010D) ACPI: FACS 0x2ff5 00040 ACPI: APIC 0x2ff40300 00054 (v1 A M I OEMAPIC 09000210 MSFT 0097) npx0: on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout acpi0: on motherboard acpi0: Power Button (fixed) Warning: ACPI is disabling APM's device. You can't run both acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu_cst0: on cpu0 acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc800-0xc8ff mem 0xff7fc000-0xff7f,0xf000-0xf3ff irq 11 at device 0.0 on pci1 uhci0: port 0xe800-0xe81f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe880-0xe89f irq 3 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xec00-0xec1f irq 5 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered pci0: (vendor 0x8086, dev 0x24cd) at device 29.7 irq 9 pcib2: at device 30.0 on pci0 pci2: on pcib2 atapci0: port 0xdc00-0xdc0f mem 0xff9f-0xff9f7fff,0xff9ffc00-0xff9ffc7f irq 10 at device 1.0 on pci2 ata2: on atapci0 ad4: 190782MB at ata2-master SATA300 ata3: on atapci0 ata4: on atapci0 ata5: on atapci0 em0: port 0xd880-0xd8bf mem 0xff9a-0xff9b,0xff9c-0xff9d irq 11 at device 12.0 on pci2 em0: MAC address: 00:07:e9:0a:5a:1f isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: on atapci1 ad0: 38166MB at ata0-master UDMA100 ata1: on atapci1 acd0: DVDROM at ata1-master UDMA33 pci0: (vendor 0x8086, dev 0x24c3) at device 31.3 irq 11 pci0: (vendor 0x8086, dev 0x24c5) at device 31.5 irq 11 pmtimer0 on isa0 fdc0: ready for input in output fdc0: cmd 3 failed at out byte 1 of 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio2: can't drain, serial port might not exist, disabling ppc1: cannot reserve I/O port range ip: MPSAFE arp: MPSAFE CAM: Configuring 6 busses CAM: finished configuring all busses (0 left) cd0 at ata5 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [256858 x 2048 byte records] Mounting root from hammer:serno/3JX139HT.s1d tryroot serno/3JX139HT.s1d Mounting devfs
Re: SiI 3124 support
On Mon, Jan 25, 2010 at 3:53 PM, Matthew Dillon wrote: > :How good is the Silicon Image 3124 chipset support in the sili(4) driver? > :Has it been well tested? > : > :Thanks, > :Tim > > I don't have a 3124 board or a machine with PCI-X slots to test with. > I believe the 3124 chipset spec is very similar to the 3132 spec which > means it should be easy to add support for the 3124 in our sili driver. > > Someone with a board and a slot is needed to do it. It might even > be possible that the only addition required is the PCI ID for the 3124 > in the sili_devices[] array in /usr/src/sys/dev/disk/sili/sili_attach.c. > > -Matt > Matthew Dillon > > I'll be getting one of these soon, so I'll let you know how it goes. Tim
SiI 3124 support
How good is the Silicon Image 3124 chipset support in the sili(4) driver? Has it been well tested? Thanks, Tim
2.4 install minor issues
2.4 looks great! The devfs stuff is very cool. I just had a couple of minor things: - On both machines I've installed, a Dimension 4500 and an Inspiron 8000, the "hit any key to reboot" after a halt doesn't cause a reboot - On a Studio 14z, I can't get either the CD or the DVD to boot using a plextor usb drive. The first dozen lines or so of boot messages appear and then the machine reboots. However, this same DVD drive boots fine with 2.4 on an Acer netbook. I haven't had any trouble with internal DVD drives. - Are devtab labels for multi-volumes with hammer working in fstab, newfs_hammer, or mount_hammer? Tim
Re: mail/mailx question
Thanks, Matt and Bill. It didn't occur to me that sendmail could be used for this. Am I correct in thinking that dma would handle this too? Tim On Tue, May 26, 2009 at 12:01 PM, Matthew Dillon wrote: > > : > :I was trying to write a mail script and couldn't find a way to set the > :"from" field to an arbitrary address. =A0Is there a way to do this with > :the base mail client? =A0I ended up installing mutt to solve the > :problem. > : > :Tim > > Normally you do it by running sendmail directly with numerous options. > Typically -f ... and -oi. I'm not sure what the options should be, > exactly. > > -Matt > Matthew Dillon >
mail/mailx question
I was trying to write a mail script and couldn't find a way to set the "from" field to an arbitrary address. Is there a way to do this with the base mail client? I ended up installing mutt to solve the problem. Tim
Re: Disk question
On Fri, May 15, 2009 at 11:17 PM, Bill Hacker wrote: > Tim Darby wrote: > >> I have a machine that was running Windows XP until I recently >> installed 2.2.2 on it. This was mainly for the purpose of trying out >> Hammer. It contains a 40GB drive, which I made the boot drive and >> installed with Hammer. The other 2 drives are a 300GB Samsung IDE and >> a 200GB Western Digital IDE, both connected to a SiI 0680 controller. >> I've succcessfully installed Hammer on the WD drive, but the Samsung >> fails as follows: >> >> # newfs_hammer -L BACKUP /dev/ad6s1a >> Volume 0 DEVICE /dev/ad6s1a size 279.46GB >> initialize freemap volume 0 >> ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=2245359 >> ad6: TIMEOUT - READ_DMA retrying (0 retries left) LBA=2245359 >> ad6: WARNING - READ_DMA status=51 >> error=84 LBA=2245359 >> newfs_hammer: get_buffer: /dev/ad6s1a:20814000 Read failed at >> offset 1149583360: Input/output error >> >> I ran a Samsung diagnostic on it and it found a DMA command timeout >> problem (service code AJ27), so it appears that the drive really does >> have a problem. Just for kicks though, I tried installing UFS on this >> drive and it gave me no complaints and seems to actually work. Also, >> Windows XP seemed to be working fine with this drive. Does that make >> any sense? >> >> Tim >> > > I don't see your Silicon Image HBA reported in dmesg all that differently > from one I am using. > > Relevant ID's from FreeBSD 7.1 AMD64 are; > > atapci0: port > 0x40a0-0x40a7,0x4094-0x4097,0x4098-0x409f,0x4090-0x4093,0x4080-0x408f > mem 0xdc04-0xdc0403ff irq 19 at device 6.0 on pci10 > > Yours form DragonFly were: > > atapci0: port > 0xec70-0xec7f,0xec90-0xec93,0xec98-0xec9f,0xeca8-0xecab,0xecb0-0xecb7 > mem 0xff1afc00-0xff1afcff irq 11 at device 11.0 on pci2 > > > Further - I've had chronic trouble of the same sort with WD, Maxtor, > Fujitsu, and Samsung drives on the Intel IHC7 (Tyan Tomcat) under FreeBSD > between 6.2 and 7.1 - not entirely absent on 7.1, either, and have moved > drives OFF the onboard IHC7 onto a cheap-as-dirt SiI PCIB HBA that runs 'em > slower, but trouble free. > > Mine has: > > atapci1: port > 0x30c0-0x30c7,0x30b4-0x30b7,0x30b8-0x30bf,0x30b0-0x30b3,0x30a0-0x30af mem > 0xdc500400-0xdc5007ff irq 19 at device 31.2 on pci0 > > > You are showing an IHC2: > > atapci1: port > 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on > pci0 > > (rest of dmesg snipped). > > > So I don't think it is the drives, and it may not be DragonFly, either. > > Intels' IHC series are as ubiquitous as housefly feces - and not a great > deal more welcome in our house these days as drive controllers go. > > HTH, > > Bill > > Thanks, Bill. I tried switching the drive ports on the Sil 0680 and no luck. I have an open IDE port on IC2, so I tried moving the problem Samsung drive there and, voila, it works fine with Hammer now. The WD drive is still working fine on the Sil 0680, so I'm leaving it there. I can only conclude at this point that the Sil and the Samsung simply can't talk DMA, for whatever reason, and I'm not inclined to chase it down. I read somewhere that if Windows XP has problems getting DMA to work, it automatically switches to PIO. Could that be why XP was OK with the original configuration? Tim
Disk question
I have a machine that was running Windows XP until I recently installed 2.2.2 on it. This was mainly for the purpose of trying out Hammer. It contains a 40GB drive, which I made the boot drive and installed with Hammer. The other 2 drives are a 300GB Samsung IDE and a 200GB Western Digital IDE, both connected to a SiI 0680 controller. I've succcessfully installed Hammer on the WD drive, but the Samsung fails as follows: # newfs_hammer -L BACKUP /dev/ad6s1a Volume 0 DEVICE /dev/ad6s1a size 279.46GB initialize freemap volume 0 ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=2245359 ad6: TIMEOUT - READ_DMA retrying (0 retries left) LBA=2245359 ad6: WARNING - READ_DMA status=51 error=84 LBA=2245359 newfs_hammer: get_buffer: /dev/ad6s1a:20814000 Read failed at offset 1149583360: Input/output error I ran a Samsung diagnostic on it and it found a DMA command timeout problem (service code AJ27), so it appears that the drive really does have a problem. Just for kicks though, I tried installing UFS on this drive and it gave me no complaints and seems to actually work. Also, Windows XP seemed to be working fine with this drive. Does that make any sense? Tim Copyright (c) 2003-2009 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly 2.2.2-RELEASE #0: Sat May 9 18:42:36 MST 2009 r...@mesquite.timdarby.com:/usr/obj/usr/src/sys/GENERIC TSC clock: 1384172980 Hz, i8254 clock: 1193158 Hz CPU: Intel(R) Pentium(R) 4 CPU 1400MHz (1384.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf07 Stepping = 7 Features=0x3febfbff real memory = 267874304 (261596K bytes) avail memory = 246792192 (241008K bytes) Preloaded elf kernel "/boot/kernel" at 0xc07c5000. Preloaded elf module "/boot/modules/acpi.ko" at 0xc07c5218. Pentium Pro MTRR support enabled md0: Malloc disk pcibios: BIOS version 2.10 Using $PIR table, 9 entries at 0xc00fbbb0 ACPI: RSDP @ 0x0xfd6d0/0x0014 (v 0 DELL ) ACPI: RSDT @ 0x0xfd6e4/0x0030 (v 1 DELLGX400 0x0005 ASL 0x0061) ACPI: FACP @ 0x0xfd718/0x0074 (v 1 DELLGX400 0x0005 ASL 0x0061) ACPI: DSDT @ 0x0xfffe5022/0x2474 (v 1 DELLdt_ex 0x1000 MSFT 0x010D) ACPI: FACS @ 0x0xff96000/0x0040 ACPI: SSDT @ 0x0xfffe75d3/0x00BA (v 1 DELLst_ex 0x1000 MSFT 0x010D) ACPI: BOOT @ 0x0xfd7e8/0x0028 (v 1 DELLGX400 0x0005 ASL 0x0061) npx0: on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout acpi0: on motherboard acpi0: Power Button (fixed) Warning: ACPI is disabling APM's device. You can't run both acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77f,0x378-0x37f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 legacypci0 on motherboard pcib0: on legacypci0 pci0: on pcib0 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pcib2: at device 30.0 on pci0 pci2: on pcib2 em0: port 0xecc0-0xecff mem 0xff1c-0xff1d,0xff1e-0xff1f irq 10 at device 8.0 on pci2 em0: MAC address: 00:07:e9:0a:5a:1f pci2: (vendor=0x16ec, dev=0x2f00) at 9.0 irq 11 atapci0: port 0xec70-0xec7f,0xec90-0xec93,0xec98-0xec9f,0xeca8-0xecab,0xecb0-0xecb7 mem 0xff1afc00-0xff1afcff irq 11 at device 11.0 on pci2 ata2: on atapci0 ad4: 190782MB at ata2-master UDMA100 ata3: on atapci0 ad6: 286168MB at ata3-master UDMA100 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe880-0xe8ff mem 0xff1af800-0xff1af87f irq 11 at device 12.0 on pci2 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: MAC address: 00:b0:d0:e7:df:73 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: on atapci1 ad0: DMA limited to UDMA33, controller found non-ATA66 cable ad0: 38166MB at ata0-master UDMA33 acd0: DVDROM at ata0-slave UDMA33 ata1: on atapci1 uhci0: port 0xff80-0xff9f irq 11 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 10 uhci1: port 0xff60-0xff7f irq 9 at device
Crash in 2.2.2
I have a machine that is a pf firewall, dns, ntp, and dhcp server (nothing else running), which was running 2.0. Last week, I did a fresh install of 2.2.2 on it. Yesterday, it crashed to the debugger prompt with an uptime of approximately 4 days. Unfortunately, the person who rebooted it didn't note the error message on the screen. I never had a crash under 2.0. I realize this report is pretty useless. If the machine does this again, what should I do at the debug prompt to collect more info? Tim
Re: 3ware raid card driver
Matthew Dillon wrote: :I'm thinking of building a DF 1.8.1 machine with a 3ware 9650SE card and :was wondering if this card is going to work and what, if any, driver :limitations there are. : :Thanks, :Tim I'm not sure about that particular model. We do have drivers for the 7000/8000 (twe) and 9000 (twa) series. I have a 7506-4 IDE and two 9500S-4LP SATA 3ware controllers. I've been having problems with the 7506... I think its a known firmware bug in the 7506 where the controller can lock up when it has problems with one of its IDE drives. I have not had any problems with the 9500S's. 3ware's management application probably doesn't work under Dragonfly. I used the BIOS support to configure mine. Ultimately the new filesystem design should be able to replace the functionality, but that won't be in production until the end of the year (though I hope to get something into beta for the July release). -Matt Matthew Dillon <[EMAIL PROTECTED]> Thanks Matt. The new filesystem sounds very cool and I would definitely give it a try if it was available now. When I get this system built, I'll post my experiences with the 9650. Tim
3ware raid card driver
I'm thinking of building a DF 1.8.1 machine with a 3ware 9650SE card and was wondering if this card is going to work and what, if any, driver limitations there are. Thanks, Tim
Re: Installer question
Justin C. Sherrill wrote: On Sun, March 12, 2006 9:46 am, Tim Darby wrote: I've been looking at the DF installer this weekend and was wondering what is the easiest way to create an unattended install of the OS? Ideally, I'd like to be able to boot a CD and return some time later to a completely installed and configured base system. I haven't tried this, but it should be possible to put all installer choices in a file called "pfi.conf" (for pre-flight installer) and place it on a floppy or USB stick and have it proceed automatically. Example fo the file here, I think: http://cvs.bsdinstaller.org/cgi-bin/cvsweb.cgi/installer/root_skels/installer/etc/defaults/pfi.conf Thanks! Looking at this file, it appears to be a collection of options that affect the behavior and environment of the installer, which is a good start but doesn't seem to address the whole picture unless I'm missing something. In other words, I want to be able to automatically create the file systems and all the other things that the installer presents during an interactive install as well. Is this just a shell script that I need to create manually? How do I get the installer to launch it? Or am I approaching this from the wrong angle entirely? Tim
Installer question
I've been looking at the DF installer this weekend and was wondering what is the easiest way to create an unattended install of the OS? Ideally, I'd like to be able to boot a CD and return some time later to a completely installed and configured base system. Tim
Re: Qmail install success on 1.4; possible package bug?
[EMAIL PROTECTED] wrote: On Sat, Jan 14, 2006 at 09:22:27PM -0700, Tim Darby wrote: Thanks for the suggestions! I installed qmail totally manually, since I didn't see a DFly package for it. There is no binary package because it can't be build without patching and therefore the package is restricted. Joerg Joerg, I noticed there is a binary package for Qmail now. Thanks! I tried it, but it seemed to only partially work. That is, it installed all the binaries, but qmail-send failed to start. Qmail-smtpd and Qmail-pop3d do start. When I looked into what was going on, I found that the installer had not created the file /var/qmail/queue/lock/sendmutex. Beyond that, it hadn't created any of the subdirectories or files under /var/qmail/queue. After manually creating sendmutex, I found that qmail-send still wouldn't start and that's when I noticed that lspawn and rspawn, which send depends on, weren't starting either. I haven't had time to figure out the problem with those and they don't give any errors when they fail. Thanks again for the package work, Tim
Re: Qmail install success on 1.4; possible package bug?
Amitai Schlair wrote: > Tim Darby wrote: > >> Thanks, I got sidetracked with another project and just now getting >> back to Qmail on DFly. It appears that root, which is what this runs >> under, already has those directories in its path, so I don't think >> that's the issue. I'm not very up on RC scripts but I found that the >> following modification to the svscan.sh that came with the package >> worked: >> >> From: >> exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' >> >> exec env PATH=/usr/pkg/bin:$PATH /bin/csh -cf '/usr/pkg/bin/svscan >> /var/spool/service &' >> >> If this is not the best way to do fix this, I'd like to know, >> especially if there's a preferred DFly way of doing it. > > A pkgsrc developer brought your message to my attention. I maintain > the djbware in pkgsrc and would like to help. > > How are you installing qmail? There's a fairly good package (if I do > say so myself :-) in pkgsrc/mail/qmail that I've been happily using > for years. > > Does DragonFly have a NetBSD-derived /etc/rc.d subsystem? If so, I > highly recommend not using svscan and /service to run qmail. Instead, > try pkgsrc/mail/qmail-run, which makes qmail feel like an ordinary > BSD-style daemon, complete with rc.d scripts, knobs in /etc/rc.conf, > etc. Interesting a scheme though /service is, I can't imagine going > back to it. > > I'm not subscribed to this list; please Cc me on any replies. > > - Amitai > Thanks for the suggestions! I installed qmail totally manually, since I didn't see a DFly package for it. If the NetBSD qmail package can be used, I will by all means try it. I'm definitely not wedded to the djb daemontools. The only reason I use them is that qmail docs recommend that and so I've just always done it that way. I will definitely try out qmail-run and see how it goes. Thanks, Tim
Re: Qmail install success on 1.4; possible package bug?
Justin C. Sherrill wrote: Tim Darby wrote: I got Qmail up and running today on 1.4 and it looks good. Coming from OpenBSD and having never done anything with FreeBSD or DragonFly before, it took me quite a while to figure out where everything was, but I did it. I have to give a hearty thanks to the people who put the DragonFly handbook together; I'd have been really stuck without it. From the OpenBSD perspective, I do miss having lynx and sudo as part of the base install. Anyway, I think I've either found a package bug or it's just me being clueless, probably the latter. As part of the Qmail install, I installed the package daemontools-0.76. After I setup the service folders and rebooted, I got boot errors from svscan telling me that it couldn't start the 'supervise' processes. After some poking around, I think the problem is that the supervise program is installed by the package in /usr/pkg/bin, however that folder is not in the path of the shell command that the included /usr/local/etc/rc.d/svscan.sh script runs. When I copied supervise to /usr/sbin and rebooted, it worked fine. Here's the only command that the svscan.sh script runs: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' Good work on 1.4 btw! Tim You'll want to put /usr/pkg/bin and /usr/pkg/sbin in your path; that'll get them found. Add it to all your existing users and /usr/share/skel, I think it is, so that new users on the system get it too. There's probably other places I'm not thinking of - /etc/login.conf, .profile, etc. I thought the $PATH was changed by default; maybe I'm wrong. Thanks, I got sidetracked with another project and just now getting back to Qmail on DFly. It appears that root, which is what this runs under, already has those directories in its path, so I don't think that's the issue. I'm not very up on RC scripts but I found that the following modification to the svscan.sh that came with the package worked: From: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' To: exec env PATH=/usr/pkg/bin:$PATH /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' If this is not the best way to do fix this, I'd like to know, especially if there's a preferred DFly way of doing it. Tim
Qmail install success on 1.4; possible package bug?
I got Qmail up and running today on 1.4 and it looks good. Coming from OpenBSD and having never done anything with FreeBSD or DragonFly before, it took me quite a while to figure out where everything was, but I did it. I have to give a hearty thanks to the people who put the DragonFly handbook together; I'd have been really stuck without it. From the OpenBSD perspective, I do miss having lynx and sudo as part of the base install. Anyway, I think I've either found a package bug or it's just me being clueless, probably the latter. As part of the Qmail install, I installed the package daemontools-0.76. After I setup the service folders and rebooted, I got boot errors from svscan telling me that it couldn't start the 'supervise' processes. After some poking around, I think the problem is that the supervise program is installed by the package in /usr/pkg/bin, however that folder is not in the path of the shell command that the included /usr/local/etc/rc.d/svscan.sh script runs. When I copied supervise to /usr/sbin and rebooted, it worked fine. Here's the only command that the svscan.sh script runs: exec /bin/csh -cf '/usr/pkg/bin/svscan /var/spool/service &' Good work on 1.4 btw! Tim
Re: Final 1.4 engineering, official release will be on Saturday
Matthew Dillon wrote: I am finishing up the release engineering today and will roll an ISO for overnight distribution to our mirrors this evening, along with the necessary web pages and such. I am going to give our mirrors a day to get the ISO's before I make the web pages live so the official release is going to be on Saturday (7 Jan 2006)! I know there are some issues with regards to timezone selection, MFS specifications, pkgsrc, etc, but I think we are just going to have to live with them for this release. I will create an errata page where the issues can be listed. -Matt Woohoo! Thanks Matt, I now know what I'll be busy with this weekend. My plan for the new year is to build a couple of QMail servers using DragonFly. There shouldn't be any issues with that, right? Tim
Re: Cardbus notes
Matthew Dillon wrote: :Then I tried removing the card and re-inserting it and that seemed to :work (cool!), but is the line "last message repeated 153862 times" (see :below) really right? dhclient manages DHCP for the interface. It usually sticks around in the background in order to keep the lease renewed. It sounds like the dhclient program is going into a tight loop logging errors after you pulled the card. That is definitely a bug. It's probably eating cpu. Do a 'top' or 'systat -vm 1' to see. You can kill dhclient manually with something like 'killall -9 dhclient'. Hmm. Probably the best fix is to have dhclient exit when it gets a device not configured error, since that means the device was pulled. -Matt Yep, 'top' shows that dhclient is averaging about 60 - 70 percent CPU with syslogd consuming the rest. Thanks, Tim
Cardbus notes
Just a couple of observations fwiw - after installing 1.4 RC2, I noticed that it threw what looked like a boot error with my Xircom card, but then found it OK: Product version: 5.0 Product name: IBM | 10/100 EtherJet CardBus | IBMC-10/100 | 1.04 | Manufacturer ID: a400130181 Functions: Network Adaptor, Multi-Functioned Function Extension: 040600062925a3c5 Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 Function Extension: 0303 Function Extension: 0501 cardbus0: Invalid BAR number: 27(06) CIS reading done dc0: port 0x1000-0x107f mem 0x88002000-0x880020ff,0x88002100-0x8800217f irq 11 at device 0.0 on cardbus0 miibus0: on dc0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: MAC address: 06:00:06:29:25:a3 Then I tried removing the card and re-inserting it and that seemed to work (cool!), but is the line "last message repeated 153862 times" (see below) really right? Jan 1 05:12:31 kernel: ukphy0: detached Jan 1 05:12:31 kernel: miibus0: detached Jan 1 05:12:31 kernel: dc0: detached Jan 1 05:12:31 dhclient: receive_packet failed on dc0: Device not configured Jan 1 05:12:49 last message repeated 84561 times Jan 1 05:12:49 kernel: Product version: 5.0 Jan 1 05:12:49 kernel: Product name: IBM | 10/100 EtherJet CardBus | IBMC-10/100 | 1.04 | Jan 1 05:12:49 kernel: Manufacturer ID: a400130181 Jan 1 05:12:49 kernel: Functions: Network Adaptor, Multi-Functioned Jan 1 05:12:49 kernel: Function Extension: 040600062925a3c5 Jan 1 05:12:49 kernel: Function Extension: 0102 Jan 1 05:12:49 kernel: Function Extension: 0280969800 Jan 1 05:12:49 kernel: Function Extension: 0200e1f505 Jan 1 05:12:49 kernel: Function Extension: 0301 Jan 1 05:12:49 kernel: Function Extension: 0303 Jan 1 05:12:49 kernel: Function Extension: 0501 Jan 1 05:12:49 kernel: cardbus0: Invalid BAR number: 27(06) Jan 1 05:12:49 kernel: CIS reading done Jan 1 05:12:49 kernel: dc0: port 0x1000-0x107f mem 0x88002000-0x880020ff,0x88002100-0x8800217f irq 11 at device 0.0 on cardbus0 Jan 1 05:12:49 kernel: miibus0: on dc0 Jan 1 05:12:49 kernel: ukphy0: on miibus0 Jan 1 05:12:49 kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jan 1 05:12:49 kernel: dc0: MAC address: 06:00:06:29:25:a3 Jan 1 05:12:49 dhclient: receive_packet failed on dc0: Device not configured Jan 1 05:13:21 last message repeated 153862 times
Software install error on live CD
Happy new year! I installed 1.4 RC2 this morning and attempted to install all of the software packages on the CD. The package install failed with the following error: Execution of the command /usr/sbin/pkg_create -b pkgdb.byfile.db /mnt/tmp/pkgdb.byfile.db.tgz failed with a return code of 127. Tim
Re: Xircom cardbus NIC not working
It worked, thanks! Tim Sepherosa Ziehau wrote: This is a dc(4) card. Please try: http://leaf.dragonflybsd.org/~sephe/if_dc_xircom.diff Best Regards, sephe On 12/26/05, Tim Darby <[EMAIL PROTECTED]> wrote: Hi all and Merry Christmas! I've been watching the DF lists for awhile now and just want to thank Matt and everyone else for all the great work on DragonFly. I can't wait for upcoming new stuff, especially ZFS. I've been running OpenBSD servers for some time but I'm a noob to DF so bare with me. I tried to boot 1.4 RC1 this morning and ran into a snag with my Realport Cardbus 10/100 NIC. I hope the attached dmesg helps. Tim Copyright (c) 2003, 2004, 2005 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly 1.4.0-RELEASE #2: Fri Dec 23 13:04:39 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC TSC clock: 366645245 Hz, i8254 clock: 1193098 Hz CPU: Pentium II/Pentium II Xeon/Celeron (366.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 183836672 (179528K bytes) pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "/kernel" at 0xc06b6000. Pentium Pro MTRR support enabled md0: Malloc disk pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdf60 npx0: on motherboard npx0: INT 16 interface legacypci0 on motherboard pcib0: on legacypci0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pci0: (vendor=0x1287, dev=0x0020) at 3.0 irq 11 cbb0: at device 4.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci_cfgintr: 0:4 INTA routed to irq 11 cbb1: at device 4.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci_cfgintr: 0:4 INTB routed to irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfce0-0xfcff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 pci0: (vendor=0x125d, dev=0x1968) at 8.0 irq 5 orm0: at iomem 0xc-0xcefff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ata1-slave: ATAPI identify retries exceeded Product version: 5.0 Product name: IBM | 10/100 EtherJet CardBus | IBMC-10/100 | 1.04 | Manufacturer ID: a400130181 Functions: Network Adaptor, Multi-Functioned Function Extension: 040600062925a3c5 Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 Function Extension: 0303 Function Extension: 0501 cardbus0: Invalid BAR number: 27(06) CIS reading done cardbus0: (vendor=0x115d, dev=0x0003) at 0.0 irq 11 cbb0: CardBus card activation failed ad0: 17301MB [35152/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master PIO4 Mounting root from cd9660:cd0c cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [114288 x 2048 byte records] -- Live Free or Die
Re: Xircom cardbus NIC not working
Thanks! I'll give it a try and let you know. Tim Sepherosa Ziehau wrote: This is a dc(4) card. Please try: http://leaf.dragonflybsd.org/~sephe/if_dc_xircom.diff Best Regards, sephe
Xircom cardbus NIC not working
Hi all and Merry Christmas! I've been watching the DF lists for awhile now and just want to thank Matt and everyone else for all the great work on DragonFly. I can't wait for upcoming new stuff, especially ZFS. I've been running OpenBSD servers for some time but I'm a noob to DF so bare with me. I tried to boot 1.4 RC1 this morning and ran into a snag with my Realport Cardbus 10/100 NIC. I hope the attached dmesg helps. Tim Copyright (c) 2003, 2004, 2005 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly 1.4.0-RELEASE #2: Fri Dec 23 13:04:39 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC TSC clock: 366645245 Hz, i8254 clock: 1193098 Hz CPU: Pentium II/Pentium II Xeon/Celeron (366.67-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 183836672 (179528K bytes) pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "/kernel" at 0xc06b6000. Pentium Pro MTRR support enabled md0: Malloc disk pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdf60 npx0: on motherboard npx0: INT 16 interface legacypci0 on motherboard pcib0: on legacypci0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 pci0: (vendor=0x1287, dev=0x0020) at 3.0 irq 11 cbb0: at device 4.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci_cfgintr: 0:4 INTA routed to irq 11 cbb1: at device 4.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci_cfgintr: 0:4 INTB routed to irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfce0-0xfcff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 pci0: (vendor=0x125d, dev=0x1968) at 8.0 irq 5 orm0: at iomem 0xc-0xcefff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ata1-slave: ATAPI identify retries exceeded Product version: 5.0 Product name: IBM | 10/100 EtherJet CardBus | IBMC-10/100 | 1.04 | Manufacturer ID: a400130181 Functions: Network Adaptor, Multi-Functioned Function Extension: 040600062925a3c5 Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 Function Extension: 0303 Function Extension: 0501 cardbus0: Invalid BAR number: 27(06) CIS reading done cardbus0: (vendor=0x115d, dev=0x0003) at 0.0 irq 11 cbb0: CardBus card activation failed ad0: 17301MB [35152/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master PIO4 Mounting root from cd9660:cd0c cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: cd present [114288 x 2048 byte records]
Re: DP performance
> I wonder why it is that important 'who' Danial Thom is, or even > whoMatthew Dillon is, in this kind of discussion. [...] > it shouldn't be important, and there is a simple solution to this problem... [...] It's important only in this particular discussion, especially when one party has thus far not provided any technical details. Tim
Re: DP performance
> You obviously have forgotten the original premise > of this (which is how do we get past the "wall" > of UP networking performance), and you also > obviously have no practical experience with > heavily utilized network devices, because you > seem to have no grasp on the real issues. Why don't you Google "Matt Dillon" (not the actor) and do some research before shooting your mouth off on HIS mailing list. Try adding the keywords "Best Internet" if you are search engine challenged. Tim
