Fatdog64-700rc (12 Feb 2015) [CLOSED]

[kirk]

kern.err kernel: DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:00:1d.0

SFR, Could you do a lspci -k and see what device/kernel module that is?

[SFR]

kern.err kernel: DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:00:1d.0

SFR, Could you do a lspci -k and see what device/kernel module that is?

Here's lspci:

Code: Select all

# lspci -k
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
	Subsystem: Toshiba America Info Systems Device ff00
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
	Kernel driver in use: pcieport
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
	Subsystem: Toshiba America Info Systems Device ff00
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
	Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05)
	Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05)
	Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel modules: i2c_i801
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165]
	Subsystem: Toshiba America Info Systems Device ff82
	Kernel driver in use: radeon
	Kernel modules: radeon
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] RV710/730 HDMI Audio [Radeon HD 4000 series]
	Subsystem: Toshiba America Info Systems Device ff82
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. Device 8181
	Kernel driver in use: rtl8192se
	Kernel modules: rtl8192se
0c:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
	Subsystem: Toshiba America Info Systems Device ff00
	Kernel driver in use: r8169
	Kernel modules: r8169
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
	Subsystem: Intel Corporation Device 8086
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
	Subsystem: Intel Corporation Device 8086
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
	Subsystem: Intel Corporation Device 8086
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
	Subsystem: Intel Corporation Device 8086
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
	Subsystem: Intel Corporation Device 8086
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
	Subsystem: Intel Corporation Device 8086
# 

I don't know if the info about that device is anywhere above..?
Anyway, here's something:

# lsusb -v | grep -B15 -A5 '0000:00:1d.0'

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.18
iManufacturer 3 Linux 3.18.6 ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:1d.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
#

___________

At this time I have that USB drive plugged in, but not mounted and dmesg stays clean so far.
Also, another USB drive is plugged in, mounted and is being utilized, but this one wasn't and still doesn't cause any problems.
Both drives are WD Passports (500 & 750 GiB respectively).
___________

EDIT:
Here's new log that shows the event from the very beginning:

Code: Select all

[ 5570.110523] usb 2-1.2: new high-speed USB device number 5 using ehci-pci
[ 5570.852917] usb 2-1.2: New USB device found, idVendor=1058, idProduct=0730
[ 5570.852923] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5570.852927] usb 2-1.2: Product: My Passport 0730
[ 5570.852930] usb 2-1.2: Manufacturer: Western Digital
[ 5570.852933] usb 2-1.2: SerialNumber:
[ 5570.853517] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[ 5570.853691] scsi host8: usb-storage 2-1.2:1.0
[ 5572.932659] scsi 8:0:0:0: Direct-Access     WD       My Passport 0730 1012 PQ: 0 ANSI: 6
[ 5572.933013] sd 8:0:0:0: Attached scsi generic sg5 type 0
[ 5575.306801] scsi 8:0:0:1: Enclosure         WD       SES Device       1012 PQ: 0 ANSI: 6
[ 5575.307160] sd 8:0:0:0: [sdc] 976707584 512-byte logical blocks: (500 GB/465 GiB)
[ 5575.308405] sd 8:0:0:0: [sdc] Write Protect is off
[ 5575.308416] sd 8:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 5575.309772] sd 8:0:0:0: [sdc] No Caching mode page found
[ 5575.309776] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 5575.311176] scsi 8:0:0:1: Attached scsi generic sg6 type 13
[ 5575.328540]  sdc: sdc1
[ 5575.331026] sd 8:0:0:0: [sdc] Attached SCSI disk
[11315.681561] ehci-pci 0000:00:1d.0: swiotlb buffer is full (sz: 32768 bytes)
[11315.681565] DMA: Out of SW-IOMMU space for 32768 bytes at device 0000:00:1d.0
[11315.681874] ehci-pci 0000:00:1d.0: swiotlb buffer is full (sz: 32768 bytes)
[11315.681876] DMA: Out of SW-IOMMU space for 32768 bytes at device 0000:00:1d.0
[11315.682171] ehci-pci 0000:00:1d.0: swiotlb buffer is full (sz: 32768 bytes)
[11315.682174] DMA: Out of SW-IOMMU space for 32768 bytes at device 0000:00:1d.0
[and so on...]

1. @5570 I plugged the drive in.
2. It remained unmounted for some time.
3. Then I mounted it and left for some time.
4. And then, @11315, unmounted and mounted again.

Greetings!

[Billtoo]

Installed to the hard drive of my emachines D620 laptop:

video-info-glx 1.5.3 Fri 13 Feb 2015 on Fatdog64 700 Linux 3.18.6 x86_64
5.0 VGA compatible controller:
Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270]
oem: ATI ATOMBIOS
product: RS690 01.00

X Server: Xorg Driver: radeon
X.Org version: 1.16.3
dimensions: 1280x800 pixels (338x211 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RS690
OpenGL version string: 2.1 Mesa 10.4.3

AMD Athlon(tm) Processor 2650e
Core 0: @800 MHz

Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

No problems so far.

[kirk]

Thanks Bill.

SFR, I think that's a usb 2.0 controller. There was a couple of storage drivers that were not built in and one usb 3.0 host controller. That will be fixed for final and we'll be going with the latest 3.18.x kernel unless 3.18 proves too problematic. We build in all of usb storage modules for a few reasons, not that it should matter if you're not using it for your savefile. Let me know if it's not usb 2.0. Also I assume that the usb drive that's causing problems has no problems in other systems.

[Ted Dog]

Suspend not working with AMD drivers, lift lid and nothing but blank screen system seems alive.

[Doglover]

How sweet it is. Thanks guys for a very excellent and polished product. My primary distro (:-

[James C]

...main problem is that the best resolution I can get is1024x768 instead of the desired 1920x1080,regardless of driver used.

I had the same or similar problem, solved:

Control Panel > Desktop > Display Properties
or just

Code: Select all

zarfy

There I always have to click VGA-0 to get the desired 1920x1080 into the combo box.

Hope that helps

Gave it a try but nothing apparent to improve things.The only resolutions that appear in the combo box are 1024x768 and 800x600.Thanks for the idea though.

When I try xorgwizard "x" will not start with nouveau at any resolution, even the 1024x768 Fatdog originally booted into. Same for "nv" and "modesetting". Once in Xorgwizard I'm forced into vesa to get a display.

No problem on the older cards though.

[James C]

Fresh install on an old dual-core with an older Nvidia card...correct resolution out of the box...no problem.

[James C]

Code: Select all

-Computer-
Processor		: 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory		: 4048MB (355MB used)
Machine Type		: Physical machine
Operating System		: Fatdog64 [700rc]
User Name		: root (root)
Date/Time		: Sat Feb 14 00:13:58 2015
-Display-
Resolution		: 1440x900 pixels
OpenGL Renderer		: Gallium 0.4 on NVA8
X11 Vendor		: The X.Org Foundation
-Audio Devices-
Audio Adapter		: HDA-Intel - HDA NVidia
Audio Adapter		: HDA-Intel - HDA NVidia

Code: Select all

-Display-
Resolution		: 1440x900 pixels
Vendor		: The X.Org Foundation
Version		: 1.16.3
-Monitors-
Monitor 0		: 1440x900 pixels
Vendor		: nouveau
Renderer		: Gallium 0.4 on NVA8
Version		: 3.0 Mesa 10.4.3
Direct Rendering		: Y_es

Code: Select all

VGA compatible controller		: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])

Just for debugging purposes, both Nvidia machines working ootb are GeForce 210 cards using VGA. The problem card is a GTX-750 using HDMI.

[Ted Dog]

Other reports of AMD chips overheating after Linux K v 3.18.1

https://bbs.archlinux.org/viewtopic.php?id=192255&p=2

[jamesbond]

2. "snapmergepuppy still breaks CUPS (the /var case)."
Because I couldn't figure out how to reproduce this.
Can you please note down the actual steps? e.g. boot (with savefile=ram), start cups, snapmerge ... etc

Ok, here's the step-by-step procedure I just performed in VBox:
1. Fresh boot from ISO, no savefile.
2. Installed FD to sda1 (ext4).
3. Added 'savefile=ram:local' in extlinux.conf to enforce PUPMODE=13
4. Reboot (+ create a savefile - plain ext4 in my case) + remove ISO.
5. Launch Seamonkey.
6. Enter localhost:631 and click "Administration" tab - it's ok.
7. Close Seamonkey and repeat no. 5-6 to see it's still ok, but do 'break' at some point.
8. Save session.
9. Launch Seamonkey, enter localhost:631 and click "Administration" tab - "Internal Server Error".

Thanks, fixed. Actually you only need to exclude /var/run, not the entire /var.

Is there a script that does the mounting or something, or it is built into the binary? If it is in the script, can we work out the script instead?

No, there's only a binary. I just checked and it simply calls the mount script.
For now I have dointst.sh in my TC package that creates that missing symlink during installation.

I built patched truecrypt, changing "ntfs" to "ntfs-3g" during mounting, this should allow it to work without changes. But I don't have any NTFS truecrypt based files to test. Do you have a small one to test?

#
# busybox blkid /dev/sr1
/dev/sr1: LABEL="WD Unlocker" TYPE="udf"
# [/code]
The last SUMMARY & VOLABEL are sr1.

That is odd! busybox blkid gets the volume label but not the udev handler. What's the complete content of /tmp/udev-fatdog-drive-icon/devices/sr1?

That's a way, too, thanks for the tip.
But for now I have just modified the AppRun to my needs, however I also tried:
1. Switch to VT-2
2. Login
3. vlock
and it seems to be ok as well...

Yes, that works too. I forgot about vlock (though I'm actually using it elsewhere... )

@James C, thanks for the test. Things like this happens from time to time, unfortunately Each kernel release brings good and bad news. Good thing is that it is easy to change Fatdog's kernel, so you can stick to the known good one and yet have everything else new.

@Ted Dog: does enabling the radeon driver bring down the temp a little? It should, no?

@L18L: the i18n firefox updater won't work with en* languages. I use en_AU, so it gets simplified to "en", but there is no "en" in firefox download dir (nor is there en-AU) - the closest one is en-GB.

cheers!

[L18L]

@L18L: the i18n firefox updater won't work with en* languages. I use en_AU, so it gets simplified to "en", but there is no "en" in firefox download dir (nor is there en-AU) - the closest one is en-GB.

I will re-work it.
Checking available languages....

[L18L]

Checking available languages....

With this

Code: Select all

### generic helpers
get_config() {
	if [ $(id -u) -ne 0 ]; then
		msg "$(gettext 'You must be root.')"
		exit 1
	fi
	
	LIBDIR=lib64 # lib for 32-bit
	ARCH=x86_64 # i686 for 32-bit
	FFCHANNEL=latest # or latest-esr
	FF_DOWNLOAD_PATH_DIR="http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/$FFCHANNEL/linux-$ARCH/"

	#FFLANG=en-US # or others
    read FFLANG < ${FATDOG_STATE_DIR}/language ; FFLANG=${FFLANG%.*}
    # FFLANG=${FFLANG//_/-} # dash cannot do this
    FFLANG=`echo ${FFLANG} | tr '_' '-'`
    [ "`curl --get ${FF_DOWNLOAD_PATH_DIR}${FFLANG} | grep '404 Not Found'`" ] && FFLANG=${FFLANG%-*}
    [ "`curl --get ${FF_DOWNLOAD_PATH_DIR}${FFLANG} | grep '404 Not Found'`" ] && FFLANG=en-US

	FF_DOWNLOAD_PATH="http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/$FFCHANNEL/linux-$ARCH/$FFLANG/"
    #echo FF_DOWNLOAD_PATH=$FF_DOWNLOAD_PATH ; exit # debug only
}

it should work.

Tested:

Code: Select all

# update-firefox.sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   262  100   262    0     0    566      0 --:--:-- --:--:-- --:--:--   565
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   287  100   287    0     0    610      0 --:--:-- --:--:-- --:--:--   611
FF_DOWNLOAD_PATH=http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/linux-x86_64/de/
#

[SFR]

SFR, I think that's a usb 2.0 controller. There was a couple of storage drivers that were not built in and one usb 3.0 host controller. That will be fixed for final and we'll be going with the latest 3.18.x kernel unless 3.18 proves too problematic. We build in all of usb storage modules for a few reasons, not that it should matter if you're not using it for your savefile. Let me know if it's not usb 2.0. Also I assume that the usb drive that's causing problems has no problems in other systems.

All USB controllers are 2.0, however this particular drive is both 2.0 & 3.0 compatibile and yes, I have never had problems with that drive and (according to smartctl) it's perfectly health.
May I ask which drivers ought to be added, so I could try to recompile vmlinuz by myself?
___________

I built patched truecrypt, changing "ntfs" to "ntfs-3g" during mounting, this should allow it to work without changes. But I don't have any NTFS truecrypt based files to test. Do you have a small one to test?

Here's 2MiB one and the password is test:
http://www.datafilehost.com/d/8a5cf8a4

But you could also do it yourself - just create a small volume (no matter how formatted), then, while mounting, press "Options" button and check "Do not mount" checkbox at the bottom.
Then mkfs.ntfs /dev/mapper/truecryptX (where X is slot number).
After that just unmount it and mount again the usual way.
___________

That is odd! busybox blkid gets the volume label but not the udev handler. What's the complete content of /tmp/udev-fatdog-drive-icon/devices/sr1?

Code: Select all

# cat /tmp/udev-fatdog-drive-icon/devices/sr0
DRIVENAME='sr0'
DEVNAME='/dev/sr0'
DRIVE_TYPE='optical'
SUMMARY=' 4GiB'
VOLABEL=''
# 
# cat /tmp/udev-fatdog-drive-icon/devices/sr1
DRIVENAME='sr1'
DEVNAME='/dev/sr1'
DRIVE_TYPE='optical-usb'
SUMMARY=' 25MiB'
VOLABEL=''
# 
# busybox blkid /dev/sr0 /dev/sr1
/dev/sr0: LABEL="NOSFERATU" TYPE="udf"
/dev/sr1: LABEL="WD Unlocker" TYPE="udf"
# 

Greetings!

[smokey01]

When clicking on a link in Notecase it opens Abiword instead of the browser.

PeasyDisc does not create an ISO when creating a slideshow under video tab. Something missing.

Hardinfo hangs when clicking on USB. I have both USB 2.0 and 3.0 on this laptop HP ProBook 4540.

[jamesbond]

Here's 2MiB one and the password is test:
http://www.datafilehost.com/d/8a5cf8a4

But you could also do it yourself - just create a small volume (no matter how formatted), then, while mounting, press "Options" button and check "Do not mount" checkbox at the bottom.
Then mkfs.ntfs /dev/mapper/truecryptX (where X is slot number).
After that just unmount it and mount again the usual way.

Thanks, I was looking for that option (mount the container but not the filesystem - I know I could do that in Windows).

Patch works and is attached.
___________

#
# busybox blkid /dev/sr0 /dev/sr1
/dev/sr0: LABEL="NOSFERATU" TYPE="udf"
/dev/sr1: LABEL="WD Unlocker" TYPE="udf"
#

All looks good, so I don't understand why the label isn't showing up. With the disk already inside, can you try to run this:

Code: Select all

udevadm trigger --sysname-match=sr0

, see if you've got the labels showing.

@smokey1 - I'll look at that, thanks.

[L18L]

@L18L: the i18n firefox updater won't work with en* languages. I use en_AU, so it gets simplified to "en", but there is no "en" in firefox download dir (nor is there en-AU) - the closest one is en-GB.

I will re-work it.
Checking available languages....

...done

EDIT
see http://murga-linux.com/puppy/viewtopic. ... 3&start=42

[SFR]

Patch works and is attached.

Yeah, works for me, too, thanks! And thanks for simplifying the building process (-ldl and pkcs stuff).
___________

Code: Select all

udevadm trigger --sysname-match=sr0

No difference...
Btw, is this the script that is called when a device gets plugged in: /usr/sbin/fatdog-drive-icon-udev-handler.sh or something else?
I'm asking because I added xmessage "test" at the very beginning of this script...and it's not being executed (even after reboot) when I'm plugging in/out devices...
___________

[EDIT]

Also, another USB drive is plugged in, mounted and is being utilized, but this one wasn't and still doesn't cause any problems.

Nope, it just happened twice also to this drive...

Greetings!

[Billtoo]

@Ted Dog: does enabling the radeon driver bring down the temp a little? It should, no?

I'm using the radeon driver with my emachines laptop and it doesn't run hot:

AMD Athlon(tm) Processor 2650e

[kirk]

All USB controllers are 2.0, however this particular drive is both 2.0 & 3.0 compatibile and yes, I have never had problems with that drive and (according to smartctl) it's perfectly health.
May I ask which drivers ought to be added, so I could try to recompile vmlinuz by myself?

These will be changed from modules to built-in:

CONFIG_USB_XHCI_PLATFORM=y
CONFIG_USB_STORAGE_ONETOUCH=y
CONFIG_USB_STORAGE_KARMA=y
CONFIG_USB_STORAGE_CYPRESS_ATACB=y
CONFIG_USB_UAS=y
CONFIG_USB_DWC3=y

But if you're not using it for your savefile/folder it shouldn't matter. We build-in the usb storage drivers because we need them available before the main sfs is mounted. But this can cause a problem if there's a kernel bug that causes the wrong driver to get used, usually overlapping device ids, then you can't unload the offending module. But I don't think that's the case here. Did this drive work fine in 700b2 (kernel-3.17.1)?