Error Dmg Aborting Because No Mount Point Found

04.05.2018

Error Dmg Aborting Because No Mount Point Found 2017
Error Dmg Aborting Because No Mount Point Found Dead
Error Dmg Aborting Because No Mount Point Found In Nc
Error Dmg Aborting Because No Mount Point Found In Texas

Dataprotector: Not a valid mount point = aborting.I recently came across the following error when setting up a new DP backup for a Windows Server 2003. Disk Mounted Graphics or DMG is considered as the one most crucial component of Mac system which contains the graphical record of your entire disk data. Using this signification features you can easily mount and manage your Mac volumes as well the all the data stored on your hard drive. Well, sometimes it.

On my TiBook DiskCopy works fine, as it has for some time on my B&W G3 with G4 upgrade. All of a sudden today the B&W will not mount a.dmg image.
Nov 08, 2007 This discussion is archived. 0 Replies Latest reply on Nov 8, 2007 5:44 PM by 595077. Not a valid mount point = aborting.

Ok. So my problem is this.
My MacBook Pro became unresponsive, when I booted, it gave a question mark on the white screen instead of starting Snow Leopard. Still don't know why, but that isn't really important now.
When this happened I got my snow leopard cd, put it in, and made a .dmg of the drive, just in case I could retrieve something. Then proceeded to format the drive.
Now, when I try to mount the .dmg, the finder says: unrecognized filesystem. Cannot mount it through the terminal either. I am wondering, is there anything I can do? I am not really versed in the terminal commands so I am not sure what is possible at this point. I would really like to get my data back though.

[DiskWarrior http://www.alsoft.com/DiskWarrior/index.html] may be able to repair the disk image, if the problem is simply a damaged disk image. If it's something worse than that, you may not have any luck.
How did you make the disk image? If you selected your hard drive, which was damaged, and clicked New Image, you've probably just created an image of a damaged disk, which may or may not be repairable. In the future, a more appropriate way to create an emergency backup in this situation is to use the Restore tab in Disk Utility. Despite the name, it does both backups and restores.. not the kind of thing I'd want to rely on for everyday backups, but it's good for emergencies.
Of course, you'd be better off to never let yourself get into that situation. Start backing up regularly. If you're not sure how, take a look at my [Mac Backup Guide http://www.reedcorner.net/thomas/guides/backups>.

Error dmg aborting because no mount point found dead

Similar Messages

Hi!
I get this strange error when connecting my external drive:
org.freedesktop.Hal.Device.Volume.UnknownFailure: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg tail or so
dmesg tail says this:
EXT4-fs warning (device sdb1): ext4_fill_super: extents feature not enabled on this filesystem, use tune2fs.
EXT4-fs: sdb1: couldn't mount because of unsupported optional features (4000400).
EXT4-fs warning (device sdb1): ext4_fill_super: extents feature not enabled on this filesystem, use tune2fs.
EXT4-fs: sdb1: couldn't mount because of unsupported optional features (4000400).
I didn't touch the external drive for some weeks now (it worked perfectly last time). It is ext3 by the way, not ext4.
So - before i use tune2fs or something like it i thought: Better ask before i lose data or worse..
Thanks in advance, Hauke
Hi!
Thanks for the answers, i still couldn't solve the problem..
First: I don't have a mke2fs.conf.pacnew, only the original which reads as follows:
[defaults]
base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
blocksize = 4096
inode_size = 256
inode_ratio = 16384
[fs_types]
ext3 = {
features = has_journal
ext4 = {
features = has_journal,extents,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
inode_size = 256
ext4dev = {
features = has_journal,extents,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
inode_size = 256
options = test_fs=1
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
floppy = {
blocksize = 1024
inode_size = 128
inode_ratio = 8192
news = {
inode_ratio = 4096
largefile = {
inode_ratio = 1048576
blocksize = -1
largefile4 = {
inode_ratio = 4194304
blocksize = -1
hurd = {
blocksize = 4096
inode_size = 128
Then after considering the risks i tried this:
e2fsck -b 8193 /dev/sdb1
This comes out, and it has no effect:
bash-3.2# e2fsck -b 8193 /dev/sdb1
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: Bad magic number in super-block beim Versuch, /dev/sdb1 zu öffnen
SuperBlock ist unlesbar bzw. beschreibt kein gültiges ext2
Dateisystem. Wenn Gerät gültig ist und ein ext2
Dateisystem (kein swap oder ufs usw.) enthält, dann ist der SuperBlock
beschädigt, und sie könnten e2fsck mit einem anderen SuperBlock:
e2fsck -b 8193 <Gerät>
Which translates to 'Bad magic number in super-block while trying to open /dev/sdb1
Superblock is not readable or describes no valid ext2 filesystem. If device is valid and contains a ext2 (which it does) then the superblock is damaged and could be replaced by another SuperBlock:
e2fsck -b 8193 <device>
(which didn't work..)
And yes, other mediums (fat32, ext3) do work
After the recent system update, Finder now freezes whenever I try to mount a dmg. In Console, the log for hdiejectd just says 'running', and I can no longer do anything with Finder, windows no longer refresh if I move them around the screen. If I relaunch Finder via Terminal, then the mounted disk image shows up, and Finder becomes functional again. But this is annoying to have to do every time! Is there a better fix out there please?
Also, had to relaunch Finder in Terminal, because if I tried to relaunch in GUI when it's frozen, I get a 'the application finder can't be opened (-10810)' error. gah!
I dunno why, but since a little why Arch stopped working because it just stops the initscripts where it checks for filesystems.
I'm getting at the beginning of initscripts this:
'Using static /dev filesystem'
Then it goes into maintenance mode after the Filesystem Check, asking for my root password, with the root filesystem mounted read-only, then it asks me to fsck it and change the superblock, however I can't do this because /dev/sda1 (my root FS) doesn't exists.
What should I do?
Thanks in advance
Chrome was acting oddly after the install - not connecting with some site and services - so I deleted it and reinstalled it. The download wouldn't run because the system considers it to be unsigned, but it installed after I overrode the security restrictions. Get more done with the new Google Chrome. A more simple, secure, and faster web browser than ever, with Google’s smarts built-in. Download now. Google chrome dmg won& 39.
1. when you start it will say filesystem check error and ask if you want to fix it type in your root password and press enter
2. type mount -o -n remount,rw / and press enter
3. type pacman -S initscripts and press enter
4. type cp /etc/rc.local.shutdown.pacsave /etc/rc.local.shutdown press enter
5. type cp /etc/rc.local.pacsave /etc/rc.local press enter
6. type cp /etc/rc.conf.pacsave /etc/rc.conf press enter
7. type cp /etc/inittab.pacsave /etc/inittab
8. type reboot and press enter and you should be able to boot into your filesystem
if you pacman tells you that it cant find initscripts then download the package from here:
ftp://ftp.archlinux.org/testing/os/i686 … pkg.tar.gz
and put it on a usb drive and mount it from inside another linux for example a ubuntu live cd
then mount your arch root aswell and copy the initscripts-2008.02-1-i686.pkg.tar.gz to mountpoint/root/
then go back and go from step 3 but with pacman -U initscripts-2008.02-1-i686.pkg.tar.gz
Last edited by INCSlayer (2008-03-01 07:25:15)
Trying to mount a share on a Windows Server I have in my home.
When I use:
smbclient -L SERVERNAME -U administrator
and I enter the password after the prompt
It returns a list of all the shares in the server like so:
Domain=[SERVERNAME] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Sharename Type Comment
SHARE1 Disk Shared folder
SHARE2 Disk Shared folder
SHARE3 Disk Shared folder
Domain=[SERVERNAME] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
Server Comment
Workgroup Master
but when I try to mount of the shares with
# mount -t cifs //SERVERNAME/SHARE1 /mnt/mountpoint -o user=administrator,password=password
it returns an error
mount error: could not resolve address for SERVERNAME: Unknown error
Am I doing something wrong?
Thanks,
the SERVERNAME in these commands is a netbiosname and can differ from the hostname.
Smbclient seems to use it's own method to resolve netbiosnames, possibly the mount command uses a different method.
Try the mount command with the ip-address of the server instead of SERVERNAME to verify mounting the share works.
If the share can be mounted by //ip-address/SHARE1 , you may need additional options for the mount command to make netbios name resolution work correctly.
check man mount.cifs .
edit : typo's
Last edited by Lone_Wolf (2013-08-10 12:40:47)
Looking for some help on a weird one here.
I recently upgraded my Intel iMac to Snow Leopard and iPhoto '09 from Leopard and iPhoto '08. Recently, I've been getting an occasional error message when trying import images that have been scanned and placed in a folder in my Pictures folder.
Scenario #1 - I tried to import a folder with 7 different PNG images in it. iPhoto started the import process and then brought up an error message stating 'Unreadable Files: 6 The following files could not be imported. (The file is in an unrecognized format.).' What I don't understand is that it imported one of the images. If it recognizes one PNG file, why not all of them? All were scanned at same time with same settings. I don't believe it's PNG specific and the next instance will explain why
Scenario #2 - I tried to share some images out of my iPhoto '09 library with my wife who is running a MacBook w/ iPhoto '08. I dragged an event directly to my drop box folder. She launched iPhoto and tried to import those images. Of the 154 images (all JPG's), she kept getting an error message that 27 of them were an 'unrecognized format'.
As an FYI..my existing iPhoto Library has 21,250 images in it. I was once told by an Apple Store employee that they have seen many times that iPhoto starts to act weird after a photo library reaches 20,000+ images. Not sure if that's true, but thought I'd mention it.
Anyone have any ideas here? This is really frustrating because I have a lot of historical images I need to scan and import. I don't want to fight this problem through that entire process.
Thanks in advance for the help and have a great day.
Joe
Hey there TD..sorry for delay, but I've been too tied up lately to try the new account idea. Going to do that later and thanks again for all of your help.
With that said, thanks to all for the feedback and comments. There is some very interesting stuff going on here, but I don't believe my issue is solely related to B/W images. I believe there is some validity to that theory, but not solely. Of the original 7 images that I scanned in Image Capture, 6 of the 7 were B/W and the only one that successfully imported was a Color image. To dispute that theory, the 2nd scenario I mentioned above was all Color images that were originally imported from my Nikon D90 (RGB format). I was copying those images from one machine to another and then tried to import them when I got those images. Machine they came from was running iPhoto 09' and machine they were going to was running iPhoto 08'.
I have gone back to scanning those B/W images in Epson Scan (finally got Epson to straighten that issue out). What I noticed during this last round is if I tried to import a large number of images, I'd get an error on a few of them. My work-around has been to only import 4 or 5 images at a time. Since doing that, I have had no issues with importing any of my B/W scans.
Again, thanks to all for the help and I'll keep you posted if I notice anything else that may seem to contribute. Take care and have a great day.
Joe
Hello---I have an iMac 10.5.8. Today I began converting old 8mm home movies onto DVD by use of a Toshiba. I am importing non-commercial DVDs into iMovie. I was so proud of myself when I figured out (through use of old forum) how to take the DVD and create a new image and mount into iMovie '08 (7.1.4). I did this successfully first try and was on cloud nine. Now editing can begin.
Well, feeling on a roll I went for a second 8mm and got it onto a DVD. Went through all the steps (application, utility, disk utilities etc.) now it is sitting as a .dmg file on desktop, same as before. This time, however, after I launch iMovie and double-click the .dmg home movie----iMovie will read 'Generating Thumbnails' for a few seconds and the blue bar will appear as if it is a 1/3 done and it will suddenly quit and this is the message I get:
(Oops. Picture missing. Edited to add message reads: 'The application iMovie quit unexpectedly. Mac OS X and other application are not affected.'
I tried to report the problem to Apple but it says it can't be done at this time and retry. What I can't figure out is I have done it already and it worked fine. I shut the computer down for a while and I came back to looked at some other ideas/posts but most were way too advanced for my knowledge and I didn't come across any with same exact issue anyhow. They may be there, but I didn't come across. I followed some posts that were close and I checked my HD in disk utilites and it came back my HD appears to be working fine so didn't seem to be anything to repair.
Can anyone give me a kindergarten explanation of how to correct this so I can continue putting .dmg files into iMovie? Why did it work just hours previously but not now?
As always, thanks for your help.
You need to convert the VOB files in the TS-Folder of the DVD back to DV which iMovie is designed to handle. For that you need mpegStreamclip:
http://www.squared5.com/svideo/mpeg-streamclip-mac.html
which is free, but you must also have the Apple mpeg2 plugin :
http://www.apple.com/quicktime/mpeg2/
(unless you are running Lion in which case see below))
which is a mere $20.
Another possibility is to use DVDxDV:
http://www.dvdxdv.com/NewFolderLookSite/Products/DVDxDV.overview.htm
which costs $25.
For the benefit of others who may read this thread:
Obviously the foregoing only applies to DVDs you have made yourself, or other home-made DVDs that have been given to you. It will NOT work on copy-protected commercial DVDs, which in any case would be illegal.
If you are running Lion:
From the MPEG Streamclip homepage
The installer of the MPEG-2 Playback Component may refuse to install the component in Lion. Apple states the component is unnecessary in Lion, however MPEG Streamclip still needs it.
To install the component in Lion, please download MPEG Streamclip 1.9.3b7 beta above; inside the disk image you will find the Utility MPEG2 Component Lion: use it to install the MPEG-2 Playback Component in Lion. The original installer's disk image (QuickTimeMPEG2.dmg) is required.
The current versions of MPEG Streamclip cannot take advantage of the built-in MPEG-2 functionality of Lion. For MPEG-2 files you still need to install the QuickTime MPEG-2 Playback Component, which is not preinstalled in Lion. You don't have to install QuickTime 7.
I downloaded the iDisk Utility for XP, ran the install, opened the Utlity, it asked for iDisk account and password, I entered both. The process started, about half way through it paused...and then, boom, a descriptive error message stating that 'iDisk Utility failed to mount your iDisk'. Thanks for stating the obvious.
Any ideas why I can't get this to mount? By the way, I confirmed that my PC is running Windows XP.
You should probably post your quiestion in the .Mac discussions:
http://discussions.apple.com/category.jspa?categoryID=116
I'm having trouble with my filesystem(s) on startup. These problems began after I cleaned my case using compressed air / vacuum, though I don't think I jostled any hardware. My original filesystem was set up like this:
/dev/sda1 NTFS WinXP partition
/dev/sda2 XFS /var
/dev/sda3 EXT3 root
/dev/sda4 extended
/dev/sda5 EXT3 /home
/dev/sda6 swap
/dev/sdb1 XFS /digitalmedia
On startup, UDev starts and Modules are loaded, then I make it to:
:: Checking Filesystems [BUSY]
/dev/sda3: clean, 87750/977280 files, 668803/3905803 blocks
/dev/sda5 is mounted. e2fsck: Cannot continue, aborting.
/sbin/fsck.xfs: XFS file system. [FAIL]
*** FILESYSTEM CHECK FAILED ***
* Please repair manually and reboot *
<snip>
If I log in as root, /proc/mounts contains this:
rootfs / rootfs rw 0 0
proc /proc prox rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=256615,mode=755 0 0
/dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 / ext3 ro,noatime,errors=continue,barrier=0,data=writeback 0 0
/dev/sdb1 /media/usbhd-sdb1 xfs rw,relatime,attr2,noquota 0 0
/dev/sda5 /media/usbhd-sda5 ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
/dev/sda1 /media/usbhd-sda1 ntfs ro,relatime,uid=0,gid=100,umask=02,nls=utf8,errors=continue,mft_zone_multiplier=1 0 0
/dev/sda2 /media/usbhd-sda2 xfs rw,relatime,attr2,noquota 0 0
As you can see, 4 partitions are mounted under /media/* instead of their appropriate locations. At this point, I rebooted to SystemRescue LiveCD and issued e2fsck -f commands for the (unmounted) EXT3 partitions:
[email protected] /proc % e2fsck -f /dev/sda3
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda3: 87750/977280 files (1.0% non-contiguous), 668803/3905803 blocks
[email protected] /proc % e2fsck -f /dev/sda5
e2fsck 1.41.12 (17-May-2010)
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being
incorrectly set) Fix<y>? yes
Superblock last write time is in the future.
(by less than a day, probably due to the hardware clock being
incorrectly set). Fix<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 7092/2564096 files (7.1% non-contiguous), 3262832/10253478 blocks
as well as xfs_check and xfs_repair commands for the (unmounted) XFS partitions:
[email protected] /proc % xfs_check /dev/sda2
[email protected] /proc % xfs_check /dev/sdb1
[email protected] /proc % xfs_repair /dev/sda2
Phase 1 - find and verify superblock..
Phase 2 - using internal log
- zero log..
- scan filesystem freespace and inode maps..
- found root inode chunk
Phase 3 - for each AG..
- scan and clear agi unlinked lists..
- process known inodes and perform inode discovery..
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes..
Phase 4 - check for duplicate blocks..
- setting up duplicate extent list..
- check for inodes claiming duplicate blocks..
- agno = 0
- agno = 2
- agno = 1
- agno = 3
Phase 5 - rebuild AG headers and trees..
- reset superblock..
Phase 6 - check inode connectivity..
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ..
- traversal finished ..
- moving disconnected inodes to lost+found ..
Phase 7 - verify and correct link counts..
done
[email protected] /proc % xfs_repair /dev/sdb1
Phase 1 - find and verify superblock..
Phase 2 - using internal log
- zero log..
- scan filesystem freespace and inode maps..
- found root inode chunk
Phase 3 - for each AG..
- scan and clear agi unlinked lists..
- process known inodes and perform inode discovery..
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- process newly discovered inodes..
Phase 4 - check for duplicate blocks..
- setting up duplicate extent list..
- check for inodes claiming duplicate blocks..
- agno = 1
- agno = 0
- agno = 2
- agno = 3
Phase 5 - rebuild AG headers and trees..
- reset superblock..
Phase 6 - check inode connectivity..
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ..
- traversal finished ..
- moving disconnected inodes to lost+found ..
Phase 7 - verify and correct link counts..
done
[email protected] /proc %
but that doesn't seem to help. I went back to check if the UUIDs in fstab were correct, and they appear to be. Here's fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=216defa9-66be-4a21-940a-2899111b6f9a swap swap defaults 0 0
UUID=8c0d304b-8c4d-4d8d-a60b-0a2e08dbfd2c /home ext3 defaults,noatime 0 1
UUID=dc4661ec-06bf-46a7-ac7d-ba183f39f402 / ext3 defaults,noatime 0 1
UUID=e09984c8-9f9f-46f9-a1c7-e4b5ed6ea1c0 /var xfs defaults 0 1
#UUID=130a944d-1094-4cde-9af3-90a840290698 /digitalmedia xfs defaults,noatime 000 1
#UUID=F0D8093AD8090098 /winxp NTFS defaults,noatime 0 0
And here's the output for fdisk-l, mount, and dmesg:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3f353f35
Device Boot Start End Blocks Id System
/dev/sda1 * 63 152151614 76075776 7 HPFS/NTFS
/dev/sda2 152151615 503718074 175783230 83 Linux
/dev/sda3 503718075 534964499 15623212+ 83 Linux
/dev/sda4 534964500 625137344 45086422+ 5 Extended
/dev/sda5 534964563 616992389 41013913+ 83 Linux
/dev/sda6 616992453 625137344 4072446 82 Linux swap / Solaris
Disk /dev/sdb: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005007d
Device Boot Start End Blocks Id System
/dev/sdb1 63 1250258624 625129281 83 Linux
mount
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=256615,mode=755)
/dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 on / type ext3 (rw,noatime,errors=continue,barrier=0,data=writeback)
shm on /dev/shm type tmpfs (rw,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/sda3 on /media/usbhd-sda3 type ext3 (rw,relatime)
/dev/sdb1 on /media/usbhd-sdb1 type xfs (rw,relatime)
/dev/sda1 on /media/usbhd-sda1 type ntfs (ro,relatime,utf8,gid=100,umask=002)
/dev/sda5 on /media/usbhd-sda5 type ext3 (rw,relatime)
/dev/sda2 on /media/usbhd-sda2 type xfs (rw,relatime)
mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
It's possible that information reported by mount(8) is not
up to date. For actual information about system mount points
check the /proc/mounts file
dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.36-ARCH ([email protected]) (gcc version 4.5.1 20101125 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010
Command line: root=/dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 ro vga=773
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)
BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
NX (Execute Disable) protection: active
DMI 2.5 present.
Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) > (reserved)
e820 update range: 0000000000000000 - 0000000000001000 (usable) > (reserved)
e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
No AGP bridge found
last_pfn = 0x7fee0 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CCFFF write-protect
CD000-EFFFF uncachable
F0000-FFFFF write-through
MTRR variable ranges enabled:
0 base 000000000 mask F80000000 write-back
1 base 07FF00000 mask FFFF00000 uncachable
2 disabled
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Scanning 0 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009f400 (usable)
modified: 000000000009f400 - 00000000000a0000 (reserved)
modified: 00000000000f0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 000000007fee0000 (usable)
modified: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
modified: 000000007fee3000 - 000000007fef0000 (ACPI data)
modified: 000000007fef0000 - 000000007ff00000 (reserved)
modified: 00000000e0000000 - 00000000f0000000 (reserved)
modified: 00000000fec00000 - 0000000100000000 (reserved)
initial memory mapped : 0 - 20000000
found SMP MP-table at [ffff8800000f39f0] f39f0
init_memory_mapping: 0000000000000000-000000007fee0000
0000000000 - 007fe00000 page 2M
007fe00000 - 007fee0000 page 4k
kernel direct mapping tables up to 7fee0000 @ 16000-1a000
RAMDISK: 37e02000 - 37ff0000
ACPI: RSDP 00000000000f7970 00014 (v00 IntelR)
ACPI: RSDT 000000007fee3000 00034 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: FACP 000000007fee3080 00074 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: DSDT 000000007fee3100 04EC3 (v01 INTELR AWRDACPI 00001000 MSFT 0100000E)
ACPI: FACS 000000007fee0000 00040
ACPI: MCFG 000000007fee80c0 0003C (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: APIC 000000007fee8000 00084 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: SSDT 000000007fee8a20 00380 (v01 PmRef CpuPm 00003000 INTL 20041203)
ACPI: Local APIC address 0xfee00000
[ffffea0000000000-ffffea0001bfffff] PMD -> [ffff880002000000-ffff880003bfffff] on node 0
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal empty
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0007fee0
On node 0 totalpages: 523887
DMA zone: 56 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3927 pages, LIFO batch:0
DMA32 zone: 7109 pages used for memmap
DMA32 zone: 512795 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x03] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
SMP: Allowing 4 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 40
early_res array is doubled to 64 at [18180 - 1897f]
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
Allocating PCI resources starting at 7ff00000 (gap: 7ff00000:60100000)
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
PERCPU: Embedded 28 pages/cpu @ffff880001a00000 s86016 r8192 d20480 u524288
pcpu-alloc: s86016 r8192 d20480 u524288 alloc=1*2097152
pcpu-alloc: [0] 0 1 2 3
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 516722
Kernel command line: root=/dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 ro vga=773
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Checking aperture..
No AGP bridge found
Calgary: detecting Calgary via BIOS EBDA area
Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Subtract (48 early reservations)
#1 [0001000000 - 00017fb9a8] TEXT DATA BSS
#2 [0037e02000 - 0037ff0000] RAMDISK
#3 [00017fc000 - 00017fc0ee] BRK
#4 [00000f3a00 - 0000100000] BIOS reserved
#5 [00000f39f0 - 00000f3a00] MP-table mpf
#6 [000009ec00 - 00000f20d4] BIOS reserved
#7 [00000f22a8 - 00000f39f0] BIOS reserved
#8 [00000f20d4 - 00000f22a8] MP-table mpc
#9 [0000010000 - 0000012000] TRAMPOLINE
#10 [0000012000 - 0000016000] ACPI WAKEUP
#11 [0000016000 - 0000018000] PGTABLE
#12 [00017fc100 - 00017fd100] BOOTMEM
#13 [0000018000 - 0000018180] BOOTMEM
#14 [0001ffe000 - 0001fff000] BOOTMEM
#15 [0001fff000 - 0002000000] BOOTMEM
#16 [0002000000 - 0003c00000] MEMMAP 0
#17 [00017fd100 - 0001815100] BOOTMEM
#18 [0001815100 - 000182d100] BOOTMEM
#19 [000182e000 - 000182f000] BOOTMEM
#20 [00017fb9c0 - 00017fba03] BOOTMEM
#21 [00017fba40 - 00017fbc70] BOOTMEM
#22 [00017fbc80 - 00017fbce8] BOOTMEM
#23 [00017fbd00 - 00017fbd68] BOOTMEM
#24 [00017fbd80 - 00017fbde8] BOOTMEM
#25 [00017fbe00 - 00017fbe68] BOOTMEM
#26 [00017fbe80 - 00017fbee8] BOOTMEM
#27 [00017fbf00 - 00017fbf68] BOOTMEM
#28 [00017fbf80 - 00017fbfe8] BOOTMEM
#29 [000182d100 - 000182d168] BOOTMEM
#30 [000182d180 - 000182d1e8] BOOTMEM
#31 [000182d200 - 000182d220] BOOTMEM
#32 [000182d240 - 000182d287] BOOTMEM
#33 [000182d2c0 - 000182d307] BOOTMEM
#34 [0001a00000 - 0001a1c000] BOOTMEM
#35 [0001a80000 - 0001a9c000] BOOTMEM
#36 [0001b00000 - 0001b1c000] BOOTMEM
#37 [0001b80000 - 0001b9c000] BOOTMEM
#38 [000182d340 - 000182d348] BOOTMEM
#39 [000182d380 - 000182d388] BOOTMEM
#40 [000182d3c0 - 000182d3d0] BOOTMEM
#41 [000182d400 - 000182d420] BOOTMEM
#42 [000182d440 - 000182d570] BOOTMEM
#43 [000182d580 - 000182d5d0] BOOTMEM
#44 [000182d600 - 000182d650] BOOTMEM
#45 [000182f000 - 0001837000] BOOTMEM
#46 [0001b9c000 - 0001d9c000] BOOTMEM
#47 [0001837000 - 0001937000] BOOTMEM
Memory: 2052920k/2096000k available (3685k kernel code, 452k absent, 42628k reserved, 2089k data, 504k init)
SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:2304
Console: colour dummy device 80x25
console [tty0] enabled
allocated 20971520 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Fast TSC calibration using PIT
Detected 2550.007 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency. 5102.51 BogoMIPS (lpj=8500023)
pid_max: default: 32768 minimum: 301
Security Framework initialized
TOMOYO Linux initialized
AppArmor: AppArmor disabled by boot time parameter
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
mce: CPU supports 6 MCE banks
CPU0: Thermal monitoring enabled (TM2)
using mwait in idle threads.
Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
.. version: 2
.. bit width: 40
.. generic registers: 2
.. value mask: 000000ffffffffff
.. max period: 000000007fffffff
.. fixed-purpose events: 3
.. event mask: 0000000700000003
ACPI: Core revision 20100702
Setting APIC routing to flat
.TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz stepping 07
NMI watchdog enabled, takes one hw-pmu counter.
Booting Node 0, Processors #1
NMI watchdog enabled, takes one hw-pmu counter.
#2
NMI watchdog enabled, takes one hw-pmu counter.
#3 Ok.
NMI watchdog enabled, takes one hw-pmu counter.
Brought up 4 CPUs
Total of 4 processors activated (20407.98 BogoMIPS).
devtmpfs: initialized
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: SSDT 000000007fee8140 0022A (v01 PmRef Cpu0Ist 00003000 INTL 20041203)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 0022A (v01 PmRef Cpu0Ist 00003000 INTL 20041203)
ACPI: SSDT 000000007fee8600 00152 (v01 PmRef Cpu1Ist 00003000 INTL 20041203)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 00152 (v01 PmRef Cpu1Ist 00003000 INTL 20041203)
ACPI: SSDT 000000007fee8760 00152 (v01 PmRef Cpu2Ist 00003000 INTL 20041203)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 00152 (v01 PmRef Cpu2Ist 00003000 INTL 20041203)
ACPI: SSDT 000000007fee88c0 00152 (v01 PmRef Cpu3Ist 00003000 INTL 20041203)
ACPI: Dynamic OEM Table Load:
ACPI: SSDT (null) 00152 (v01 PmRef Cpu3Ist 00003000 INTL 20041203)
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
PCI: Using host bridge windows from ACPI; if necessary, use 'pci=nocrs' and report a bug
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
pci_root PNP0A08:00: host bridge window [mem 0x000c0000-0x000dffff]
pci_root PNP0A08:00: host bridge window [mem 0x7ff00000-0xfebfffff]
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:1a.0: reg 20: [io 0xff00-0xff1f]
pci 0000:00:1a.1: reg 20: [io 0xfe00-0xfe1f]
pci 0000:00:1a.2: reg 20: [io 0xfd00-0xfd1f]
pci 0000:00:1a.7: reg 10: [mem 0xfdfff000-0xfdfff3ff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10: [mem 0xfdff8000-0xfdffbfff 64bit]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.0: PME# disabled
pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.1: PME# disabled
pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
pci 0000:00:1c.2: PME# disabled
pci 0000:00:1d.0: reg 20: [io 0xfc00-0xfc1f]
pci 0000:00:1d.1: reg 20: [io 0xfb00-0xfb1f]
pci 0000:00:1d.2: reg 20: [io 0xfa00-0xfa1f]
pci 0000:00:1d.7: reg 10: [mem 0xfdffe000-0xfdffe3ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: [io 0x0400-0x047f] claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: [io 0x0480-0x04bf] claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0290 (mask 0007)
pci 0000:00:1f.2: reg 10: [io 0xf900-0xf907]
pci 0000:00:1f.2: reg 14: [io 0xf800-0xf803]
pci 0000:00:1f.2: reg 18: [io 0xf700-0xf707]
pci 0000:00:1f.2: reg 1c: [io 0xf600-0xf603]
pci 0000:00:1f.2: reg 20: [io 0xf500-0xf50f]
pci 0000:00:1f.2: reg 24: [io 0xf400-0xf40f]
pci 0000:00:1f.3: reg 10: [mem 0xfdffd000-0xfdffd0ff 64bit]
pci 0000:00:1f.3: reg 20: [io 0x0500-0x051f]
pci 0000:00:1f.5: reg 10: [io 0xf200-0xf207]
pci 0000:00:1f.5: reg 14: [io 0xf100-0xf103]
pci 0000:00:1f.5: reg 18: [io 0xf000-0xf007]
pci 0000:00:1f.5: reg 1c: [io 0xef00-0xef03]
pci 0000:00:1f.5: reg 20: [io 0xee00-0xee0f]
pci 0000:00:1f.5: reg 24: [io 0xed00-0xed0f]
pci 0000:01:00.0: reg 10: [mem 0xfa000000-0xfaffffff]
pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:01:00.0: reg 1c: [mem 0xf8000000-0xf9ffffff 64bit]
pci 0000:01:00.0: reg 24: [io 0xaf00-0xaf7f]
pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0: bridge window [io 0xa000-0xafff]
pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfbffffff]
pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
pci 0000:00:1c.0: bridge window [mem 0xfdb00000-0xfdbfffff]
pci 0000:00:1c.0: bridge window [mem 0xfd900000-0xfd9fffff 64bit pref]
pci 0000:03:00.0: reg 10: [io 0xdf00-0xdf07]
pci 0000:03:00.0: reg 14: [io 0xde00-0xde03]
pci 0000:03:00.0: reg 18: [io 0xdd00-0xdd07]
pci 0000:03:00.0: reg 1c: [io 0xdc00-0xdc03]
pci 0000:03:00.0: reg 20: [io 0xdb00-0xdb0f]
pci 0000:03:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.1: bridge window [mem 0xfd800000-0xfd8fffff]
pci 0000:00:1c.1: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
pci 0000:04:00.0: reg 10: [mem 0xfddfc000-0xfddfffff 64bit]
pci 0000:04:00.0: reg 18: [io 0xbe00-0xbeff]
pci 0000:04:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:04:00.0: supports D1 D2
pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:04:00.0: PME# disabled
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2: bridge window [io 0xb000-0xbfff]
pci 0000:00:1c.2: bridge window [mem 0xfdd00000-0xfddfffff]
pci 0000:00:1c.2: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
pci 0000:05:03.0: reg 10: [mem 0xfdae0000-0xfdaeffff]
pci 0000:05:03.0: reg 14: [io 0xcf00-0xcf1f]
pci 0000:05:04.0: reg 10: [mem 0xf4000000-0xf7ffffff pref]
pci 0000:05:05.0: reg 10: [mem 0xfdaff000-0xfdafffff]
pci 0000:05:05.0: supports D1 D2
pci 0000:05:05.0: PME# supported from D0 D1 D2 D3hot
pci 0000:05:05.0: PME# disabled
pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:1e.0: bridge window [mem 0xfda00000-0xfdafffff]
pci 0000:00:1e.0: bridge window [mem 0xf4000000-0xf7ffffff 64bit pref]
pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
pci 0000:00:1e.0: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
pci 0000:00:1e.0: bridge window [mem 0x7ff00000-0xfebfffff] (subtractive decode)
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PEX0._PRT]
ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PEX1._PRT]
ACPI: PCI Interrupt Routing Table [_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 *7 9 10 11 12)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 *4 5 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 10 *11 12)
HEST: Table is not found!
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
reserve RAM buffer: 000000000009f400 - 000000000009ffff
reserve RAM buffer: 000000007fee0000 - 000000007fffffff
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: [io 0x04d0-0x04d1] has been reserved
system 00:01: [io 0x0290-0x030f] has been reserved
system 00:01: [io 0x0880-0x088f] has been reserved
system 00:07: [io 0x0400-0x04bf] could not be reserved
system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
system 00:0a: [mem 0x000f0000-0x000fffff] could not be reserved
system 00:0a: [mem 0x7ff00000-0x7fffffff] has been reserved
system 00:0a: [mem 0x7fee0000-0x7fefffff] could not be reserved
system 00:0a: [mem 0x00000000-0x0009ffff] could not be reserved
system 00:0a: [mem 0x00100000-0x7fedffff] could not be reserved
system 00:0a: [mem 0xfec00000-0xfec00fff] could not be reserved
system 00:0a: [mem 0xfed14000-0xfed1dfff] has been reserved
system 00:0a: [mem 0xfed20000-0xfed9ffff] has been reserved
system 00:0a: [mem 0xfee00000-0xfee00fff] has been reserved
system 00:0a: [mem 0xffb00000-0xffb7ffff] has been reserved
system 00:0a: [mem 0xfff00000-0xffffffff] has been reserved
system 00:0a: [mem 0x000e0000-0x000effff] has been reserved
pci 0000:01:00.0: BAR 6: assigned [mem 0xfb000000-0xfb01ffff pref]
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0: bridge window [io 0xa000-0xafff]
pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfbffffff]
pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
pci 0000:00:1c.0: PCI bridge to [bus 02-02]
pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
pci 0000:00:1c.0: bridge window [mem 0xfdb00000-0xfdbfffff]
pci 0000:00:1c.0: bridge window [mem 0xfd900000-0xfd9fffff 64bit pref]
pci 0000:03:00.0: BAR 6: assigned [mem 0xfde00000-0xfde0ffff pref]
pci 0000:00:1c.1: PCI bridge to [bus 03-03]
pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
pci 0000:00:1c.1: bridge window [mem 0xfd800000-0xfd8fffff]
pci 0000:00:1c.1: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
pci 0000:04:00.0: BAR 6: assigned [mem 0xfdc00000-0xfdc1ffff pref]
pci 0000:00:1c.2: PCI bridge to [bus 04-04]
pci 0000:00:1c.2: bridge window [io 0xb000-0xbfff]
pci 0000:00:1c.2: bridge window [mem 0xfdd00000-0xfddfffff]
pci 0000:00:1c.2: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
pci 0000:00:1e.0: PCI bridge to [bus 05-05]
pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:1e.0: bridge window [mem 0xfda00000-0xfdafffff]
pci 0000:00:1e.0: bridge window [mem 0xf4000000-0xf7ffffff 64bit pref]
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:01.0: setting latency timer to 64
pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:1c.0: setting latency timer to 64
pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
pci 0000:00:1c.1: setting latency timer to 64
pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
pci 0000:00:1c.2: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff]
pci_bus 0000:00: resource 8 [mem 0x7ff00000-0xfebfffff]
pci_bus 0000:01: resource 0 [io 0xa000-0xafff]
pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfbffffff]
pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
pci_bus 0000:02: resource 0 [io 0x9000-0x9fff]
pci_bus 0000:02: resource 1 [mem 0xfdb00000-0xfdbfffff]
pci_bus 0000:02: resource 2 [mem 0xfd900000-0xfd9fffff 64bit pref]
pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
pci_bus 0000:03: resource 1 [mem 0xfd800000-0xfd8fffff]
pci_bus 0000:03: resource 2 [mem 0xfde00000-0xfdefffff 64bit pref]
pci_bus 0000:04: resource 0 [io 0xb000-0xbfff]
pci_bus 0000:04: resource 1 [mem 0xfdd00000-0xfddfffff]
pci_bus 0000:04: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
pci_bus 0000:05: resource 0 [io 0xc000-0xcfff]
pci_bus 0000:05: resource 1 [mem 0xfda00000-0xfdafffff]
pci_bus 0000:05: resource 2 [mem 0xf4000000-0xf7ffffff 64bit pref]
pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7]
pci_bus 0000:05: resource 5 [io 0x0d00-0xffff]
pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff]
pci_bus 0000:05: resource 7 [mem 0x000c0000-0x000dffff]
pci_bus 0000:05: resource 8 [mem 0x7ff00000-0xfebfffff]
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
UDP hash table entries: 1024 (order: 3, 32768 bytes)
UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
NET: Registered protocol family 1
pci 0000:01:00.0: Boot video device
PCI: CLS 64 bytes, default 64
Unpacking initramfs..
Freeing initrd memory: 1976k freed
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1294574252.469:1): initialized
HugeTLB registered 2 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 4013
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xf9000000, mapped to 0xffffc90010100000, using 1536k, total 14336k
vesafb: mode is 1024x768x8, linelength=1024, pages=3
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
intel_idle: MWAIT substates: 0x20
intel_idle: does not run on family 6 model 23
ERST: Table is not found!
Linux agpgart interface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
rtc_cmos 00:03: RTC can wake from S4
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, 242 bytes nvram
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
PM: Resume from disk failed.
registered taskstats version 1
rtc_cmos 00:03: setting system clock to 2011-01-09 11:57:33 UTC (1294574253)
Initalizing network drop monitor service
Freeing unused kernel memory: 504k freed
udev[45]: starting version 164
SCSI subsystem initialized
libata version 3.00 loaded.
pata_acpi 0000:00:1f.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
pata_acpi 0000:00:1f.2: setting latency timer to 64
pata_acpi 0000:00:1f.2: PCI INT A disabled
ata_piix 0000:00:1f.2: version 2.13
ata_piix 0000:00:1f.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Floppy drive(s): fd0 is 1.44M
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.2: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0xf900 ctl 0xf800 bmdma 0xf500 irq 19
ata2: SATA max UDMA/133 cmd 0xf700 ctl 0xf600 bmdma 0xf508 irq 19
ata_piix 0000:00:1f.5: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
ata_piix 0000:00:1f.5: setting latency timer to 64
scsi2 : ata_piix
scsi3 : ata_piix
ata3: SATA max UDMA/133 cmd 0xf200 ctl 0xf100 bmdma 0xee00 irq 19
ata4: SATA max UDMA/133 cmd 0xf000 ctl 0xef00 bmdma 0xee08 irq 19
FDC 0 is a post-1991 82077
pata_acpi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pata_acpi 0000:03:00.0: setting latency timer to 64
pata_acpi 0000:03:00.0: PCI INT A disabled
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD6400AAKS-65A7B2, 01.03B01, max UDMA/133
ata2.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
ata1.00: ATA-7: MAXTOR STM3320620AS, 3.AAE, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA MAXTOR STM332062 3.AA PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access ATA WDC WD6400AAKS-6 01.0 PQ: 0 ANSI: 5
pata_jmicron 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
pata_jmicron 0000:03:00.0: setting latency timer to 64
scsi4 : pata_jmicron
scsi5 : pata_jmicron
ata5: PATA max UDMA/100 cmd 0xdf00 ctl 0xde00 bmdma 0xdb00 irq 17
ata6: PATA max UDMA/100 cmd 0xdd00 ctl 0xdc00 bmdma 0xdb08 irq 17
sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
sd 1:0:0:0: [sdb] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI disk
sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: [sda] Attached SCSI disk
ata5.00: ATAPI: _NEC DVD_RW ND-3550A, 1.05, max UDMA/33
ata5.00: configured for UDMA/33
scsi 4:0:0:0: CD-ROM _NEC DVD_RW ND-3550A 1.05 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda3): mounted filesystem with writeback data mode
Not activating Mandatory Access Control now since /sbin/tomoyo-init doesn't exist.
udev[761]: starting version 164
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
i801_smbus 0000:00:1f.3: PCI INT B -> GSI 18 (level, low) -> IRQ 18
iTCO_vendor_support: vendor-support=0
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
sky2: driver version 1.28
sky2 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
sky2 0000:04:00.0: setting latency timer to 64
sky2 0000:04:00.0: Yukon-2 EC Ultra chip revision 3
sky2 0000:04:00.0: irq 40 for MSI/MSI-X
sky2 0000:04:00.0: eth0: addr 00:50:8d:b3:2b:d6
input: PC Speaker as /devices/platform/pcspkr/input/input0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sr 4:0:0:0: Attached scsi generic sg2 type 5
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: irq 41 for MSI/MSI-X
HDA Intel 0000:00:1b.0: setting latency timer to 64
hda_codec: ALC888: BIOS auto-probing.
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input1
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ACPI: acpi_idle registered with cpuidle
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfdfff000
uhci_hcd: USB Universal Host Controller Interface driver
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfdffe000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff00
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000fe00
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000fd00
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000fc00
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000fb00
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000fa00
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
ACPI: Power Button [PWRF]
Linux video capture interface: v2.00
ivtv: Start initialization, version 1.4.2
ivtv0: Initializing card 0
ivtv0: Autodetected Hauppauge card (cx23416 based)
ivtv 0000:05:04.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THRM] (45 C)
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
tveeprom 1-0050: Hauppauge model 26582, rev F0B2, serial# 9304267
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25843 (idx 37)
tveeprom 1-0050: decoder processor is CX25843 (idx 30)
tveeprom 1-0050: has no radio
ivtv0: Autodetected Hauppauge WinTV PVR-150
cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
ACPI: Fan [FAN] (on)
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
usb 3-2: new full speed USB device using uhci_hcd and address 2
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
tuner-simple 1-0061: creating new instance
tuner-simple 1-0061: type set to 50 (TCL 2002N)
ivtv0: Registered device video0 for encoder MPG (4096 kB)
ivtv0: Registered device video32 for encoder YUV (2048 kB)
ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
ivtv0: Registered device video24 for encoder PCM (320 kB)
ivtv0: Initialized card: Hauppauge WinTV PVR-150
flexcop-pci: will use the HW PID filter.
flexcop-pci: card revision 2
ivtv: End initialization
b2c2_flexcop_pci 0000:05:03.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
b2c2_flexcop_pci 0000:05:03.0: setting latency timer to 64
------------[ cut here ]------------
WARNING: at fs/proc/generic.c:323 __xlate_proc_name+0xbd/0xe0()
Hardware name: .
name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
Modules linked in: tuner_simple tuner_types wm8775 tuner fan cx25840 snd_seq_dummy firewire_ohci(+) firewire_core crc_itu_t snd_seq_oss b2c2_flexcop_pci(+) b2c2_flexcop dvb_core cx24123 cx24113 s5h1420 ivtv cx2341x v4l2_common videodev v4l1_compat v4l2_compat_ioctl32 i2c_algo_bit tveeprom snd_seq_midi_event snd_seq snd_seq_device thermal button uhci_hcd processor ehci_hcd usbcore snd_hda_codec_realtek snd_pcm_oss snd_mixer_oss snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc psmouse evdev sg pcspkr sky2 iTCO_wdt iTCO_vendor_support i2c_i801 i2c_core shpchp serio_raw pci_hotplug intel_agp ext3 jbd mbcache sr_mod cdrom sd_mod pata_jmicron floppy ata_piix pata_acpi libata scsi_mod
Pid: 2310, comm: modprobe Tainted: P 2.6.36-ARCH #1
Call Trace:
[<ffffffff81054f7a>] warn_slowpath_common+0x7a/0xb0
[<ffffffff81055051>] warn_slowpath_fmt+0x41/0x50
[<ffffffff81189c9d>] __xlate_proc_name+0xbd/0xe0
[<ffffffff81189d30>] __proc_create+0x70/0x140
[<ffffffff8118a769>] proc_mkdir_mode+0x29/0x60
[<ffffffff8118a7b1>] proc_mkdir+0x11/0x20
[<ffffffff810b7dcb>] register_handler_proc+0x11b/0x140
[<ffffffff810b5ae9>] __setup_irq+0x1e9/0x340
[<ffffffffa0636180>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
[<ffffffff810b5d4a>] request_threaded_irq+0x10a/0x210
[<ffffffffa06364c0>] flexcop_pci_probe+0x1b0/0x350 [b2c2_flexcop_pci]
[<ffffffff8120976a>] local_pci_probe+0x5a/0xd0
[<ffffffff81209f50>] pci_device_probe+0x80/0xb0
[<ffffffff812a4f6a>] ? driver_sysfs_add+0x7a/0xb0
[<ffffffff812a5246>] driver_probe_device+0x96/0x1c0
[<ffffffff812a540b>] __driver_attach+0x9b/0xa0
[<ffffffff812a5370>] ? __driver_attach+0x0/0xa0
[<ffffffff812a41ae>] bus_for_each_dev+0x5e/0x90
[<ffffffff812a4ee9>] driver_attach+0x19/0x20
[<ffffffff812a4a07>] bus_add_driver+0xc7/0x2e0
[<ffffffffa063a000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[<ffffffff812a5681>] driver_register+0x71/0x140
[<ffffffff8107b29d>] ? notifier_call_chain+0x4d/0x70
[<ffffffffa063a000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
[<ffffffff8120a1e1>] __pci_register_driver+0x51/0xd0
[<ffffffff8107b5fe>] ? __blocking_notifier_call_chain+0x5e/0x80
[<ffffffffa063a01e>] flexcop_pci_module_init+0x1e/0x20 [b2c2_flexcop_pci]
[<ffffffff8100212f>] do_one_initcall+0x3f/0x180
[<ffffffff8109113b>] sys_init_module+0xbb/0x200
[<ffffffff8100af42>] system_call_fastpath+0x16/0x1b
---[ end trace cea0e78273359df7 ]---
DVB: registering new adapter (FlexCop Digital TV device)
b2c2-flexcop: MAC address = 00:d0:d7:30:15:0f
CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
CX24123: wrong demod revision: 87
usb 3-2: not running at top speed; connect to a high speed hub
hub 3-2:1.0: USB hub found
hub 3-2:1.0: 4 ports detected
usb 3-2.2: new low speed USB device using uhci_hcd and address 3
nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
nvidia 0000:01:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 260.19.29 Wed Dec 8 12:08:56 PST 2010
usb 3-2.3: new low speed USB device using uhci_hcd and address 4
usbcore: registered new interface driver hiddev
input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.2/3-2.2:1.0/input/input4
generic-usb 0003:046D:C01D.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1a.0-2.2/input0
attempt to access beyond end of device
sda4: rw=0, want=4, limit=2
EXT3-fs (sda4): error: unable to read superblock
input: Generic USB K/B as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.3/3-2.3:1.0/input/input5
generic-usb 0003:13BA:0017.0002: input,hidraw1: USB HID v1.10 Keyboard [Generic USB K/B] on usb-0000:00:1a.0-2.3/input0
input: Generic USB K/B as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.3/3-2.3:1.1/input/input6
generic-usb 0003:13BA:0017.0003: input,hidraw2: USB HID v1.10 Mouse [Generic USB K/B] on usb-0000:00:1a.0-2.3/input1
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sdb1
Ending clean XFS mount for filesystem: sdb1
ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err -121)
Unknown/Unsupported NXT chip: 00 00 00 00 00
lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret -121)
ivtv0: Encoder revision: 0x02060039
bcm3510: Revision: 0x1, Layer: 0xb.
b2c2-flexcop: found 'Broadcom BCM3510 VSB/QAM frontend' .
DVB: registering adapter 0 frontend 0 (Broadcom BCM3510 VSB/QAM frontend)..
b2c2-flexcop: initialization of 'Air2PC/AirStar 2 ATSC 1st generation' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
firewire_ohci 0000:05:05.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
firewire_ohci 0000:05:05.0: setting latency timer to 64
firewire_ohci: Added fw-ohci device 0000:05:05.0, OHCI v1.0, 8 IR + 8 IT contexts, quirks 0x0
NTFS driver 2.1.29 [Flags: R/W MODULE].
NTFS-fs warning (device sda1): parse_options(): Option utf8 is no longer supported, using option nls=utf8. Please use option nls=utf8 in the future and make sure utf8 is compiled either as a module or into the kernel.
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda5): using internal journal
EXT3-fs (sda5): mounted filesystem with writeback data mode
NTFS volume version 3.1.
NTFS-fs error (device sda1): load_system_files(): Volume is dirty. Mounting read-only. Run chkdsk and mount in Windows.
XFS mounting filesystem sda2
Ending clean XFS mount for filesystem: sda2
firewire_core: created device fw0: GUID 0000010000013236, S400
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
At this point, I'm not exactly sure where the problem is. I suspect that the filesystems themselves are ok (based on the liveCD tests), so perhaps the problem is the filesystems are inappropriately mounted under /media/* when they are not supposed to (ie before fsck during startup). Also, UDev (which I assume does this mounting) thinks these partitions are USB HD type directories instead of internal SATA partitions. Finally, the errors in dmesg referring to the flexcop module might be a red herring? Please help - I'm not sure what next step to take.
Thanks for your reply. I did not disconnect any SATA leads. I mainly cleaned the CPU heatsink and fan.
I am able to boot through UDev and get to filesystems checks without the LiveCD. More specifically, on boot without the live CD, both drives are recognized by the bios and Grub 1.5 is loaded, presenting options to boot into Arch Linux, Arch Linux Fallback, or Windows. If I select Arch Linux, boot messages scroll by, then I see:
> Arch Linux
> http://www.archlinux.org
> Copyright 2002-2007 Judd Vinet
> Copyright 2007-2010 Aaron Griffin
> Distributed under the GNU General Public License (GPL)
:: Starting UDev Daemon [DONE]
:: Triggering UDev uevents [DONE]
:: Loading Modules [DONE]
:: Waiting for UDev uevents to be processed [DONE]
:: Bringing up loopback interface [DONE]
:: Mounting Root Read-only [DONE]
:: Checking Filesystems [BUSY]
/dev/sda3: clean, 87750/977280 files, 668803/3905803 blocks
/dev/sda5 is mounted. e2fsck: Cannot continue, aborting.
/sbin/fsck.xfs: XFS file system [FAIL]
***************** FILESYSTEM CHECK FAILED ****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
Give root password for maintenance
(or type Control-D to continue):
At this prompt, if I press Control-D, the system reboots. If I log in using the root password, I see a root prompt. At this point, /proc/mounts already has partitions in it under /media (again this is without any LiveCD). Each directories' contents under media seem normal.
Interestingly, as I posted above, mount reports that both /dev/disk/by-uuid/dc4661 and /dev/sda3 are mounted (to / and /media/usbhd-sda3, respectively), although this is actually the same partition.
I should mention I have also run the bootable disk utilities provided by Seagate and WD for each drive and have run their diagnostic studies, which were unrevealing (each ran for ~1.5 hours).
After seeing the sda1 error messages in dmesg, I booted to WinXP from GRUB. CHKDSK ran and the system booted normally. I ran CHKDSK again from within WinXP as well which revealed no errors. Then, booting into Arch produces a few new errors in dmesg (which are probably irrelevant to the main problem):
NTFS volume version 3.1.
NTFS-fs warning (device sda1): load_system_files(): Unsupported volume flags 0x4000 encountered.
NTFS error (device sda1): load_system_files(): Volume has unsupported flags set. Mounting read-only. Run chkdsk and mount in Windows.
I don't know if the problem is at the BIOS/hw, partition table, GRUB, UDev, etc.
Hi,
I ran into mount error when installing xcode 3.2.6 and iOS 4.3 downloaded from https://developer.apple.com/devcenter/download.action?path=/Developer_Tools/xcod e_3.2.6_and_ios_sdk_4.3__final/xcode_3.2.6_and_ios_sdk_4.3.dmg.
I work on Mac mini with Mac OS X 10.6.
Could anyone help? Thanks!
Regards,
Emily
Hi Ken,
Thanks for your advice! I would try to clean up for more free space. I just downloaded one dmg from another website linking to apple. I could successfully install that one, but very often the content in gdb window is empty. Even if the gdb works for some time initially, after loading some specific project, the gdb doesn't provide info any longer :-( Any idea?
It might be the best season in Shenzhen now. It is sunny, but not hot, with temperature from 25 degree centigrade to 30.
Regards,
Emily
I have downloaded 'Lightroom_5_LS11_mac_5_7.dmg' for Mac to update my Lightroom 5.6 (build 974614) but when I attempt to open it I get the following error message 'Lightroom_5_LS11_mac_5_7.dmg can't be opened as the disk image is not recognised'. I'm running Yosemite OS 10.10 on a Macbook Pro (Retina, 13-inch, Late 2012 with 2.9 GHz Intel Core i7 processor).
Vk2mh it sounds like the download was not complete or corrupted. Where are you downloading the update from? Have you tried downloading again?
I'm getting the following error when I want to put something in Mycloud : 6/02/12 21:00:14,689 Cloud: -[__NSCFDictionary name]: unrecognized selector sent to instance 0x1002d57c0
I'm getting the following error when I want to put something in Mycloud : 6/02/12 21:00:14,689 Cloud: -[__NSCFDictionary name]: unrecognized selector sent to instance 0x1002d57c0
I have tried 4 times at different times of the day today and the .dmg file that I double click to load comes with an error box the following disk images couldnot be opened - DesignStandard CS6 (Reason) Not Reconized.
File sizes I have one ending in .dmg.part (3.79 GB) and a other .dmg (3.78 GB both file I get the same error as above
Machines:
Power Mac 10.6.8 16GB 2 x 2.66 GHz (12 core)
Power Book 10.6.8 16GB 2.2 intel core
Its the full version purshased I get no errors when down loading I get the icon on the down loaded file as I do on all dmg files from the web (could I pay for the posts/boxed version)
I have just tried again this morning and its worked !!
I get an 'Unrecognized database format' error when trying to access addin to Acrobat reader so I can use Pro to edit a pdf document? What do I do so that teh ACCESS program aI am generating PDF's from uses Pro and not Reader?
Thanks,
Dan
Adobe Reader and Acrobat Professional are 2 different products. Reader is for free and limited as to what it can do an support.
Add-ins can only use features supported by Reader.
You need Acrobat to edit PDF forms. Acrobat no longer supports access to SQL databases through Acrobat JavaScript.
If you have an add-in and Acrobat can use it for filling a PDF form from Access, you need to talk to the developer to see if it can work with Reader.
:: Retrieving packages from core..
cracklib-2.8.19-1-i686 238.4 KiB 254K/s 00:01 [############################################################] 100%
filesystem-2012.8-1-any 5.8 KiB 4.63M/s 00:00 [############################################################] 100%
systemd-189-3-i686 1232.1 KiB 333K/s 00:04 [############################################################] 100%
systemd-sysvcompat-189-3-i686 5.4 KiB 56.7K/s 00:00 [############################################################] 100%
(4/4) checking package integrity [############################################################] 100%
(4/4) loading package files [############################################################] 100%
(4/4) checking for file conflicts [############################################################] 100%
(6/6) checking available disk space [############################################################] 100%
(1/2) removing libsystemd [############################################################] 100%
(2/2) removing systemd-tools [############################################################] 100%
(1/4) upgrading cracklib [############################################################] 100%
(2/4) upgrading filesystem [############################################################] 100%
error: extract: not overwriting dir with file var/run
error: problem occurred while upgrading filesystem
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.
Aw, yes. Thought I had already dealt with that, but this is a pretty new install, so evidently not. Thought maybe it was related to systemd, which I installed yest, and with which I have been having trouble. Anyway, thanks again.

Symptoms Of DMG File Not Acknowledged Error

The processing speed of the Mac Operating system gets slow
Running Mac programs gets terminated suddenly
Mac data get lost or become inaccessible
Files on Mac OS get corrupted or damaged
Installed programs get crashed or freeze often
Error messages prompt on the screen that “DMG not acknowledged error”.

Related Solution- How to Read DMG File on Windows

Users Queries Related To DMG Not Recognized

“I have updated my Mac OS based system. After that, when I was trying to access DMG file then an error message “DMG not recognized” appeared on my computer screen. I have tried many methods, which I know to solve this error but I failed. Please help me with the relevant solutions.”
“My Mac DMG files got corrupted due to some virus attack and due to the corruption, I cannot access those files. I have no idea how can I resolve this issue. Is there any who can help me to fix “DMG not recognized error?”

Error Dmg Aborting Because No Mount Point Found 2017

Causes Of DMG Not Acknowledged Error Message

There are various reasons behind Mac error i.e DMG not acknowledged. Due to this error user cannot open or access DMG file. Some of those causes are mentioned as below:

Mac Header File Corruption: To access Mac data header file of Mac is required. Due to the corruption of header file, the Mac data files become inaccessible.
Human Mistakes: Accidental deletion of Mac files, formatting of Mac files, closes program unintentionally are some common human mistakes, which makes Mac files corrupted or damaged. In this case, missing the Mac file issue arise.
Sudden Termination Of System: Sometimes due to power surge, Mac machine gets terminated suddenly, due to which some of the Mac files fail to mount and become unresponsive.
Virus Attacks: Mac OS is safe as compared to Windows in the matter of virus but still some nasty viruses enter into the system and make installed programs and applications inaccessible.
Problem In Boot Sector: When a problem in boot sector arise then Mac fails to load files. In this case, the system fails to open the file and file cannot be accessed situation occurred.
Improper Installation Of Program: If unwanted applications and programs are installed without checking its source and agreement then DMG not recognized error occurred.
Hardware and software issue: It is a common issue that can be quite responsible for the Mac DMG file not acknowledged error.
Interrupted Read/Write Operation: When we interrupt read/write operation in midway then it may also lead to an error of DMG not recognized.
Modification In BIOS Setting: When we make some changes in BIOS sector then it may lead DMG file not recognized the problem.
The kernel Panic Issue: kernel is the main part of Mac OS but due to corruption in Kernel user becomes fail to open the Mac DMG files or unable to start applications.

Precautions To Avoid DMG Not Recognized Situation

There are various precautions and tips are available to avoid DMG file not recognized the problem. Some of them are listed below:

Stop using Mac system at once, if DMG File Not Recognized issue arise and go for inbuilt disk recovery option.
Never overwrite the free space that has been created after deletion of Mac files.
Always have a proper backup of your saved Mac files to overcome DMG Not Recognized issue.
Always keep your Mac system update with security fixes to protect from virus
Avoid downloading software from suspicious or untrustworthy websites because the downloading of software from suspicious sites can destroy the system and can cause the error of DMG not acknowledged.
Do not restart the Mac system
Do not switch off the Mac machine to avoid DMG not acknowledged error.
Avoid updating of system files
Do not share new data after corruption issue
Always shut down your system properly
Search the Mac trash files
After performing the above steps the DMG not recognized error is resolved.

Error Dmg Aborting Because No Mount Point Found

Manual Methods To Solve DMG Not Recognized Error

Method 1: Sometimes, the error of DMG not recognized have not been resolved by performing this method. Then follow the below mentioned steps to remove the DMG file not recognized error:

Error Dmg Aborting Because No Mount Point Found Dead

Search and launch the Disk Utility
Click on check file system option
Wait till the scanning process gets over
Select the file that you want to mount it.

Error Dmg Aborting Because No Mount Point Found In Nc

Method 2: If there is a problem with the Mac system then follow the below-mentioned to fix DMG not recognized error:

Insert the Mac Bootable CD or Flash drive and then restart the system
Click on Install Mac OS X option
Continuously press the “C” button from your keyboard
Accept the license agreement and then select the desired language
Click on Macintosh HD
After that, click on Options icon to select the installation method. Further, if you want to save your personal file folders, user accounts, and networking accounts then click on Archive to Install” and select Preserve Users and Network Settings
Restart your Mac machine and reply to configuration prompt to resolve the DMG not acknowledged error.
Then, after performing all the above steps the DMG file not acknowledged error will be resolved.

Conclusion

Error Dmg Aborting Because No Mount Point Found In Texas

DMG files are required to install applications in Mac system. If DMG not acknowledged then a user cannot install any program on Mac machine. After downloading DMG file when the user tries to access that file then sometimes an error “DMG Not acknowledged” occurs on the user screen. There are various reasons behind this error such as accidental deletion of Mac files, formatting of Mac files, Mac header file corruption, virus attack, a problem in the boot sector, etc. Manually, DMG file not acknowledged error can be solved by running Disk Utility and by reinstalling Mac OS X.

Comments are closed.

dmg.update-version.download