fsck on FAT32 filesystem?
I have a sizable (200GB) external USB 2.0 interface hard drive. (Actually, it's a plain old PATA drive in one of those enclosures that allows it to speak USB 2.0.) So anyway, to make this external drive work with things other than just my FreeBSD system, the drive has been formatted so that it contains a single, all-encompassing FAT32 filesystem. For various reasons that I won't go into, the thing experienced a power fail while it was being written to. I can successfully remount it on my FreeBSD system, so apparently, the FAT32 filesystem isn't too awfully damaged... at least not in the vicinity of the root directory. But I am old school, and paranoid, so I'd really like to run the FAT32 equivalent of fsck on the thing, to clean up any filesystem glitches. Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, Jul 15, 2012 at 2:23 AM, Ronald F. Guilmette r...@tristatelogic.comwrote: Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? /sbin/fsck_msdosfs -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? fsck_msdosfs but, in spite of some fanatics here my get worried, i do recommend use windoze scandisk. When recovering data from FAT32 i've proven myself what is actually a better tool. unless your disk is badly corrupted fsck_msdosfs would be fine too. but gets funny crashes when there are thousands of losts files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Kernel panic while importing a pool
Hi, I had several kernel panics, and I finally understood that one of memory was bad. I removed it. But now, each time I try to import my pool, I get a kernel panic I'm using freebsd 9.0-release generic Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x468 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81473525 stack pointer = 0x28:0xff811c98e370 frame pointer = 0x28:0xff811c98e390 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1592 (txg_thread_enter) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x187 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x8147357e at bp_get_dsize_sync+0x3e #7 0x8145e9b0 at dsl_scan_free_cb+0x120 #8 0x81430c74 at bpobj_iterate_impl+0xd4 #9 0x81430ebb at bpobj_iterate_impl+0x31b #10 0x8145fbc3 at dsl_scan_sync+0x4c3 #11 0x814670e0 at spa_sync+0x390 #12 0x81477739 at txg_sync_thread+0x139 #13 0x8080682f at fork_exit+0x11f #14 0x80b0366e at fork_trampoline+0xe dmesg : http://privatepaste.com/5c8c738627 What else can I add to help solving this bug? I'm not very good with freebsd. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, 15 Jul 2012 10:56:22 +0200 (CEST) Wojciech Puchar articulated: Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? fsck_msdosfs but, in spite of some fanatics here my get worried, i do recommend use Window's Scandisk. If you absolutely, positively have to recover the drive, I would recommend SpinRite 6 http://www.grc.com/intro.htm. Its not free; however, I have witnessed it recovering drives that other utilities gave up on. The only problem is that if you use another utility first it may mangle up the drive so bad that SpinRite cannot correct it. Its not quick either. I have seen it take an entire week to rebuild an 80 GB drive, but it DID actually recover all of the data. The choice is yours; however, running SpinRite at its maximum strength -- 5 -- is about as good as it gets unless you want to try a commercial outlet. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On 15/07/2012 09:56, Wojciech Puchar wrote: but, in spite of some fanatics here my get worried, i do recommend use windoze scandisk. I'd forgotten about scandisk - for modern Windows (XP and newer) you'll want to use chkdsk ( e.g. 'chkdsk /F C:' ). -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? There's fsck_msdosfs, part of the base system. Regular fsck should call it automatically if you run it on a FAT filesystem. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, 15 Jul 2012, Bruce Cran wrote: On 15/07/2012 09:56, Wojciech Puchar wrote: but, in spite of some fanatics here my get worried, i do recommend use windoze scandisk. I'd forgotten about scandisk - for modern Windows (XP and newer) you'll want to use chkdsk ( e.g. 'chkdsk /F C:' ). both do the same -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
If you absolutely, positively have to recover the drive, I would recommend SpinRite 6 http://www.grc.com/intro.htm. Its not free; again i would recommend standard windows scandisk. such tools as the other utilities are usually not better. make sure you have full disk backup anyway ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On 15/07/2012 19:43, Wojciech Puchar wrote: both do the same 'scandisk' is not recognized as an internal or external command, operable program or batch file. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
In message CA+tpaK0H=L8pcSkOxxAekfy2rQV49-sWof0FDPsutb8=04b...@mail.gmail.com , Adam Vande More amvandem...@gmail.com wrote: On Sun, Jul 15, 2012 at 2:23 AM, Ronald F. Guilmette r...@tristatelogic.comwrote: Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? /sbin/fsck_msdosfs Thank you. That sure sounds like it ought to do the trick. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
In message 5002b996.2000...@cran.org.uk, Bruce Cran br...@cran.org.uk wrote: On 15/07/2012 09:56, Wojciech Puchar wrote: but, in spite of some fanatics here my get worried, i do recommend use windoze scandisk. I'd forgotten about scandisk - for modern Windows (XP and newer) you'll want to use chkdsk ( e.g. 'chkdsk /F C:' ). Thank you. I had considered maybe using scandisk/chkdsk, but I loath turning on my one and only Windoze system unless I have to. (Mostly I keep it turned off so that its inherently evil aura will not accidently leak out and perhaps contaminate any of my other equipment.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, 15 Jul 2012 20:43:57 +0200 (CEST)
Wojciech Puchar articulated:
On Sun, 15 Jul 2012, Bruce Cran wrote:
On 15/07/2012 09:56, Wojciech Puchar wrote:
but, in spite of some fanatics here my get worried, i do recommend
use windoze scandisk.
I'd forgotten about scandisk - for modern Windows (XP and newer)
you'll want to use chkdsk ( e.g. 'chkdsk /F C:' ).
^
[VOLUME[PATH]FILENAME]] /F
Use the [/R] option to recover data {implies /F}
In any case, SpinRite is a much better option.
both do the same
No they don't.
1) Unlike CHKDSK, ScanDisk would also repair cross linked files.
2) ScanDisk cannot check NTFS disk drives, and therefore it is
unavailable for computers that may be running NT based (including
Windows 2000, Windows XP, etc.) versions of Windows.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, 15 Jul 2012 11:51:57 -0700, Ronald F. Guilmette wrote: In message CA+tpaK0H=L8pcSkOxxAekfy2rQV49-sWof0FDPsutb8=04b...@mail.gmail.com , Adam Vande More amvandem...@gmail.com wrote: On Sun, Jul 15, 2012 at 2:23 AM, Ronald F. Guilmette r...@tristatelogic.comwrote: Is there any such a tool (as fsck for FAT32) available for freeBSD? If so, where would I find it? /sbin/fsck_msdosfs Thank you. That sure sounds like it ought to do the trick. It will do its job: Check the file system's integrity. From that point, you will either have the answer that everything is okay, or you have to go into the direction of recovery. In that case, different tools need to be used. For example, make an 1:1 copy using dd (or ddrescue or dd_rescue) of the disk. Work with a copy of that copy. Do not alter the disk. Then use tools that do the job of recovery (see my list postings about that topic, they contain a good list of tools you can use on UNIX). The suggestion of SpinRite is also good, even though the program is expensive. I'm confident it's worth its money. But if you are willing to _learn_ (which means to read and to experiment), the free recovery tools available through the Ports Collection are really good. Example: I had to recover data from a USB stick that Windows had repaired, so no files could be read anymore. Getting a copy of the stick required a long time (because it was already damaged), but with the help of the free programs, I could recover _all_ files from the stick, and hand them over to a happy customer. But as I said, it may be possible that you don't have to walk the rugged streets of data recovery. :-) Suggestion: First use fsck_msdosfs without any parameters so it will ONLY CHECK the disk without altering anything (also see man fsck for -n, -v and maybe -d). Addendum: For dealing with non-standard file systems (such as FAT/msdosfs), the use of the _native tools_ seems to be the best solution in most times. In exceptions, it makes things worse. Still in most situations it just does the right thing. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Is there a way to run FreeBSD ports through port 80?
Hello All, I have a similar problem with passive ftp due to a self-imposed restrictive firewall. When make fetch is run on a port and ftp data is required, the PF firewall stops the program from completing. I got around this problem by restarting the firewall with a separate set of rules that opened up more ports needed for passive ftp. After the fetch operation I would then restart PF with the more restrictive rules. This sequence works but is a pain to maintain and also opens up a large number of ports during ftp operations. I would like to have a setup in which I do not have to restart my firewall every time I need to use passive ftp. From past experience setting MASTER_SORT to http works for those ports that use http but obviously has not worked for those ports that ONLY use ftp. I tried to use ftp-proxy but as far as I'm able to ascertain it will not work on my simple home office setup. It is a single client connected to the internet via a router: host -- router -- adsl modem -- ISP. Any help to resolve this will be greatly appreciated. Cheers ... Mark On Thursday, 12 July 2012 12:23:29 Kaya Saman wrote: Hi, I am trying to introduce FreeBSD into my office and it's been looked at with quite a bit of enthusiasm however, what makes it look bad is our companies 'security' policy to block FTP. At present they are running a whole bunch of CentOS based boxes and VM's which of course can be run through port 80 when using YUM. How does one get round this issue as my superiors are telling me that opening up FTP is a security risk and therefor don't want to proceed? I would like to use ports specifically and not the pkg_add tool to get software. Can anyone sugget anything? Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, 15 Jul 2012 21:48:23 +0200 Polytropon articulated: For example, make an 1:1 copy using dd (or ddrescue or dd_rescue) of the disk. Work with a copy of that copy. Do not alter the disk. Then use tools that do the job of recovery (see my list postings about that topic, they contain a good list of tools you can use on UNIX). The suggestion of SpinRite is also good, even though the program is expensive. I'm confident it's worth its money. But if you are willing to _learn_ (which means to read and to experiment), the free recovery tools available through the Ports Collection are really good. If I might interject here, making a copy is obviously imperative; however, it also exposes a severe problem. You are working under the assumption that the copy is actually correct.In fact, it is simply what is being read from the disk at the time of the copy. It may in fact be totally in error. SpinRite will attempt to read a damage sector up to 2000 times and through different algorithms determine what is most likely the correct data. Obviously it cannot do that if it is working with a copy of the drive. It must have access to the original drive. I have to admit that am partial to SpinRite since it saved my ass twice in the past 10 years when no other software could do the job 100%. Hence, if you cannot afford to lose your data, back it up. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
totally in error. SpinRite will attempt to read a damage sector up to 2000 times and through different algorithms determine what is most man dd conv=sync,noerror ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, Jul 15, 2012 at 4:29 PM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: totally in error. SpinRite will attempt to read a damage sector up to 2000 times and through different algorithms determine what is most man dd Even better, recoverdisk /dev/da0 /dev/da1 -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
where is LOCALBASE actually defined?
$ cat Makefile all: echo $(LOCALBASE) $ $ make echo $ What do I need to do to use LOCALBASE in my makefiles? Thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: fsck on FAT32 filesystem?
On Sun, 15 Jul 2012 23:29:39 +0200 (CEST), Wojciech Puchar wrote: totally in error. SpinRite will attempt to read a damage sector up to 2000 times and through different algorithms determine what is most man dd conv=sync,noerror Even though it doesn't use different algorithms, programs like dd_rescue and ddrescue can also change the block size upon encountering read errors, and apply several cycles of read attempts. In worst case, there will be gaps in the result. Surely SpinRite is more clever than that, using some means to extrapolate the missing data. http://www.garloff.de/kurt/linux/ddrescue/ http://www.gnu.org/software/ddrescue/ddrescue.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where is LOCALBASE actually defined?
On 15 July 2012 14:47, Anton Shterenlikht me...@bristol.ac.uk wrote: $ cat Makefile all: echo $(LOCALBASE) $ $ make echo easier way to test is make -V LOCALBASE What do I need to do to use LOCALBASE in my makefiles? You need to include bsd.port.mk (found in /usr/ports/Mk) -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where is LOCALBASE actually defined?
On Sun, Jul 15, 2012 at 03:06:14PM -0700, Eitan Adler wrote: On 15 July 2012 14:47, Anton Shterenlikht me...@bristol.ac.uk wrote: $ cat Makefile all: echo $(LOCALBASE) $ $ make echo easier way to test is make -V LOCALBASE What do I need to do to use LOCALBASE in my makefiles? You need to include bsd.port.mk (found in /usr/ports/Mk) I though LOCALBASE has meaning outside of the ports system too. Clearly I was wrong. So, if I happen not to have the ports tree, I cannot use LOCALBASE in my makefiles, right? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: where is LOCALBASE actually defined?
On 15 July 2012 15:17, Anton Shterenlikht me...@bristol.ac.uk wrote: I though LOCALBASE has meaning outside of the ports system too. Clearly I was wrong. So, if I happen not to have the ports tree, I cannot use LOCALBASE in my makefiles, right? correct. LOCALBASE is a ports tree specific thing. you could define it yourself as follows: LOCALBASE?=/usr/local -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ati, radeon, dri (drm) confusion
My X behaves really weird lately [1,2], so I went back to basics. Can somebody please comment on whether what I'm doing seems correct. Thanks HP Compaq 6715s laptop FreeBSD 10.0-CURRENT #9 r238259M amd64 vgapci0@pci0:1:5:0: class=0x03 card=0x30c2103c chip=0x791f1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'RS690M [Radeon X1200 Series]' class = display subclass = VGA which, according to radeon(4x), is supported by radeon driver. I've got in the kernel, amongst other things,: device agp device drm device radeondrm device vga I then see in dmesg: $ dmesg | grep vga vgapci0: VGA-compatible display port 0x4000-0x40ff mem 0xc010-0xc80f,0 xd020-0xd020,0xd030-0xd03f irq 19 at device 5.0 on pci1 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 $ dmesg | grep -i agp $ dmesg | grep -i radeon Is this expected that there's nothing related to either agp on radeon in dmesg? Anyway, if I do X auto-configure, i.e. X -configure, I get in the resulting xorg.conf.new: Identifier Card0 Driver radeon VendorName Advanced Micro Devices [AMD] nee ATI BoardName RS690M [Radeon X1200 Series] BusID PCI:1:5:0 Is that correct? I then see in /var/log/Xorg.0.log: drmOpenDevice: node name is /dev/dri/card0 Failed to change owner or group for file /dev/dri! 2: No such file or directory Failed to change owner or group for file /dev/dri/card0! 2: No such file or dire ctory drmOpenDevice: open result is -1, (No such file or directory) Failed to change owner or group for file /dev/dri/card0! 2: No such file or dire ctory drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module radeon (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. I guess this is not good, right? Please advise [1] http://lists.freebsd.org/pipermail/freebsd-x11/2012-June/012100.html [2] http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035171.html -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ati, radeon, dri (drm) confusion
Have you tried loading the radeon kernel module from /boot/loader.conf? Or even from the console, before starting X? Adam On Mon, 2012-07-16 at 00:08 +0100, Anton Shterenlikht wrote: My X behaves really weird lately [1,2], so I went back to basics. Can somebody please comment on whether what I'm doing seems correct. Thanks HP Compaq 6715s laptop FreeBSD 10.0-CURRENT #9 r238259M amd64 vgapci0@pci0:1:5:0: class=0x03 card=0x30c2103c chip=0x791f1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'RS690M [Radeon X1200 Series]' class = display subclass = VGA which, according to radeon(4x), is supported by radeon driver. I've got in the kernel, amongst other things,: deviceagp devicedrm deviceradeondrm devicevga I then see in dmesg: $ dmesg | grep vga vgapci0: VGA-compatible display port 0x4000-0x40ff mem 0xc010-0xc80f,0 xd020-0xd020,0xd030-0xd03f irq 19 at device 5.0 on pci1 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 $ dmesg | grep -i agp $ dmesg | grep -i radeon Is this expected that there's nothing related to either agp on radeon in dmesg? Anyway, if I do X auto-configure, i.e. X -configure, I get in the resulting xorg.conf.new: Identifier Card0 Driver radeon VendorName Advanced Micro Devices [AMD] nee ATI BoardName RS690M [Radeon X1200 Series] BusID PCI:1:5:0 Is that correct? I then see in /var/log/Xorg.0.log: drmOpenDevice: node name is /dev/dri/card0 Failed to change owner or group for file /dev/dri! 2: No such file or directory Failed to change owner or group for file /dev/dri/card0! 2: No such file or dire ctory drmOpenDevice: open result is -1, (No such file or directory) Failed to change owner or group for file /dev/dri/card0! 2: No such file or dire ctory drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module radeon (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. I guess this is not good, right? Please advise [1] http://lists.freebsd.org/pipermail/freebsd-x11/2012-June/012100.html [2] http://lists.freebsd.org/pipermail/freebsd-current/2012-July/035171.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
re: Patch failed to apply cleanly [chromium-20.0.1132.57] FreeBSD 9.0-RELEASE
On Thu, 2012-07-12 at 22:33 +0300, Alexander Kapshuk wrote: When attempting to upgrade chromium-19.0.1084.56_1 to chromium-20.0.1132.57 on FreeBSD9.0 (FreeBSD box2 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386), one of the patches failed to apply: -- === Applying extra patch /usr/ports/www/chromium/files/extra-patch-gcc === Applying FreeBSD patches for chromium-20.0.1132.57 patch: malformed patch at line 15: #if PLATFORM(CHROMIUM) = Patch patch-third_party__WebKit__Source__WebCore__config.h failed to apply cleanly. -- There seems to be a patch available that has been reported as having worked on a 9.0-RELEASE/amd64: http://www.mail-archive.com/freebsd-chromium@freebsd.org/msg00340.html - www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h.orig 2012-07-12 09:19:26.0 + +++ www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h 2012-07-12 10:49:20.0 + @@ -1,6 +1,6 @@ third_party/WebKit/Source/WebCore/config.h.orig2012-05-30 10:05:35.0 +0300 -+++ third_party/WebKit/Source/WebCore/config.h 2012-06-05 22:32:48.0 +0300 -@@ -127,6 +127,11 @@ +--- third_party/WebKit/Source/WebCore/config.h.orig2012-07-10 07:52:48.0 + third_party/WebKit/Source/WebCore/config.h 2012-07-12 10:48:15.0 + +@@ -127,6 +127,14 @@ #define WTF_USE_NEW_THEME 1 #endif // PLATFORM(MAC) - Is there a patch available to an x86 based system? The same patch will work for x86. In lieu of the patch simply edit www/chromium/files/patch-third_party__WebKit__Source__WebCore__config.h and change the line: @@ -127,6 +127,11 @@ to: @@ -127,6 +127,14 @@ Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
