The Linux Thread!

[visivante]

Okay, to me it looks like a plugin issue, as the plugins use C#/Mono to work in Unity3D/KSP, the stacktrace says it's Mono at least.

Native stacktrace:

/home/aleks/Desktop/KSP104LITE/KSP_Data/Mono/x86_64/libmono.so(+0x915ee) [0x7fdd4561e5ee]

/home/aleks/Desktop/KSP104LITE/KSP_Data/Mono/x86_64/libmono.so(+0x3483b) [0x7fdd455c183b]

/lib/x86_64-linux-gnu/libpthread.so.0(+0xfc90) [0x7fdd4bd25c90]

./KSP.x86_64() [0x4346fe]

./KSP.x86_64() [0x434a3f]

./KSP.x86_64() [0x434ab8]

./KSP.x86_64() [0x43621d]

./KSP.x86_64() [0x43196c]

./KSP.x86_64() [0x433494]

./KSP.x86_64() [0x6eb5fc]

./KSP.x86_64() [0x6f4b8e]

./KSP.x86_64() [0x6f595a]

./KSP.x86_64() [0x6f27ed]

./KSP.x86_64() [0x42e09e]

/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fdd4a232ec5]

./KSP.x86_64() [0x42f891]

The Player.log actually lists two addon plugins, KAS and SCANsat, which it had trouble with.

Got a SIGSEGV while executing native code. This usually indicates

a fatal error in the mono runtime or one of the native libraries

used by your application.

=================================================================

The following assembly referenced from /home/aleks/Desktop/KSP104LITE/GameData/Fusebox/Plugins/Fusebox.dll could not be loaded:

Assembly: KAS (assemblyref_index=8)

Version: 0.5.2.0

Public Key: (none)

The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/home/aleks/Desktop/KSP104LITE/GameData/Fusebox/Plugins/).

Could not load file or assembly 'KAS, Version=0.5.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.

The following assembly referenced from /home/aleks/Desktop/KSP104LITE/GameData/Fusebox/Plugins/Fusebox.dll could not be loaded:

Assembly: SCANsat (assemblyref_index=10)

Version: 1.2.1.0

Public Key: (none)

The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/home/aleks/Desktop/KSP104LITE/GameData/Fusebox/Plugins/).

Could not load file or assembly 'SCANsat, Version=1.2.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.

GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture

The last two lines are where KSP starts loading graphics stuff.

Then near the bottom there's to null reference exceptions both saying it's SCANsat.

NullReferenceException: Object reference not set to an instance of an object

at UIListItemContainer.ScanChildren (Boolean includeInactive) [0x00000] in <filename unknown>:0

at UIListItemContainer.Start () [0x00000] in <filename unknown>:0

at UIListItemContainer.FindOuterEdges () [0x00000] in <filename unknown>:0

at UIScrollList.PositionNewItems () [0x00000] in <filename unknown>:0

at UIScrollList.InsertItem (IUIListObject item, Int32 position, System.String text, Boolean doEasing) [0x00000] in <filename unknown>:0

at UIScrollList.AddItem (IUIListObject item, System.String text) [0x00000] in <filename unknown>:0

at UIScrollList.AddItem (IUIListObject item) [0x00000] in <filename unknown>:0

at ApplicationLauncher.AddModApplication (.ApplicationLauncherButton button) [0x00000] in <filename unknown>:0

at ApplicationLauncher.AddModApplication (.OnTrue onTrue, .OnFalse onFalse, .OnHover onHover, .OnHoverOut onHoverOut, .OnEnable onEnable, .OnDisable onDisable, AppScenes visibleInScenes, UnityEngine.Texture texture) [0x00000] in <filename unknown>:0

at ConnectedLivingSpace.CLSAddon.OnGUIAppLauncherReady () [0x00000] in <filename unknown>:0

at ConnectedLivingSpace.CLSAddon.Start () [0x00000] in <filename unknown>:0

Then of course we have this.

"Using memoryadresses from more that 16GB of memory"

So I think from all that, you need to check for updates for SCANsat, and test KSP without SCANsat installed, maybe KAS as well, and if KSP doesn't crash with that "memoryadresses" error let the SCANsat modder know that something's going on.

In addition to this, the KSP.log is showing issues with the fuelswitch.

[WRN 11:31:10.556] Cannot create config from file '/home/aleks/Desktop/KSP104LITE/GameData/InterstellarFuelSwitch/Plugins/FuelSwitchConfig.cfg'.

[ERR 11:31:10.556] Error: Empty part config file

And clouds.

[EXC 11:55:52.743] NullReferenceException: Object reference not set to an instance of an object

Clouds.Clouds.Update ()

Thanks a ton for the diagnosis.

It's strange because the mods in question appear to be functioning perfectly despite these errors. Obviously if they're crashing the game they're not functioning perfectly, but they appear to be up until that point.

I know that the Clouds error is a harmless and known issue with those VFX mods, so probably don't have to worry about that one. But will certainly dig into the rest! ​I'll try what you suggested and get back with results asap.

Edit: It appears that Fusebox was having issues too, no?

Edited August 20, 2015 by visivante

[R0d1n]

Thanks again, sal-vager. Yes, I am indeed running in a virtual machine! I apologize; I did not think that would be relevant. I'm on virtualbox, using the guest additions to allow 3d hardware acceleration, etc. The underlying OS is Windows 10 64 bit, and my CPU supports Hyper-v and other forms of virtualization. I also have been using a link from the desktop, but I get the same problem even if I delete the desktop link and start from steam or by clicking in the folder directly.

Edited August 21, 2015 by R0d1n

[sal_vager]

I really don't know where to begin with running KSP in a virtual machine, or any 3D game for that matter, VM graphics drivers are not good.

Hyper-V won't guarantee your GPU can be used, it's just a feature that lets the VM use the hardware more intelligently.

VirtualBox supports both Intel's VT-x and AMD's AMD-V hardware-virtualization. Making use of these facilities, VirtualBox can run each guest VM in its own separate address-space; the guest OS ring 0 code runs on the host at ring 0 in VMX non-root mode rather than in ring 1

As you have other text rendering this issue does not look to be due to lack of a font, Ubuntu includes the arial fonts anyway, and if it was a missing font you wouldn't see a solid box, you'd not see any text at all.

It looks more like a rendering problem, the text could be applied to a sprite and being scaled to suit and the scaling is not being performed correctly.

Or more likely it's the alpha channel, I don't know about Unity specifically but some game engines will convert imported fonts into sprite sheets and they colour the "blank" area the same as the colour of the font, as this helps prevent scaling artefacts, so if the alpha is broken with font rendering all you'd see is a box.

Either way it's the graphics driver, maybe try messing with the driver settings if there are any, also note that Virtualbox says that this feature is experimental.

I don't think it's possible to change the driver in a VM, you get what you're given and if it doesn't work all you can do is wait for an update, so all I can really suggest is that you try using a different virtual machine, if you're using the open source version of Virtualbox from the Ubuntu repositories you should try the proprietary version from the Virtualbox website instead as it will have better support for the host GPU.

I don't think there's any other VM that offers 3D support and isn't a time limited trial.

Maybe consider a dual-boot ?

Edited August 21, 2015 by sal_vager

[Laie]

Oh boy. After a few weeks, I finally became aware that the KSP folder needs to be my working directory.

This is insidious, as the game seems to work. Mods load nicely, the parts are there... the missing physics.cfg is silently created in whatever happens to be your working directory and there's any amount of weird bugs and glitches, but most can be worked around.

Could someone please open a bug, that KSP should at least check it's working directory at launch time and give some notification or other?

[Poodmund]

Hey guys,

I've got KSP working for the most part on Linux with a handful of mods. I'm comfortably floating around the 5-6gb RAM usage when suddenly the game will crash on a scene change.

Checking the Player.log indicates: 'Using memoryadresses from more that 16GB of memory' as the last logged line. Which would make sense if I were actually reaching the my rigs limit of 16GB of memory. But I'm watching the Activity Monitor and memory usage never actually goes above ~6GB...

So, why would the Player.log be indicating to me that I'm running out of memory when Activity Monitor is saying the opposite?

Thanks for the help in advance!

I've been getting exactly the same issue recently on scene change like yourself with the same line output to the log. I'll catch them next time it happens and upload them here too for reference.

[steve_v]

if you're using the open source version of Virtualbox from the Ubuntu repositories you should try the proprietary version from the Virtualbox website instead as it will have better support for the host GPU.

AFAICT, the only thing the non-GPL (PUEL) licensed version brings is USB2 support. Though it may still be worth looking at if it's a few versions ahead of the packages in the repos.

Maybe consider a dual-boot ?

Yeah, it's going to work better with a real GPU.

Edited August 24, 2015 by steve_v

[legolegs]

Hello there, I've got a piece of information to be possibly added to the first post:

How to change mouse polling rate in linux temporarily without rebooting

There is a special virtual file to checking out and setting this parameter. You must work with it using terminal being root.

Read value:

[root@localhost~]# cat /sys/module/usbhid/parameters/mousepoll 
0

It says 0 (zero) which means 1 milliseconds (almost zero) of delay between system's requests to mouse which means good aiming in games. But in KSP it also means that while right mouse button pressed game tries to redraw screen 1000 times per second which is impossible. That's why KSP lags when rotating camera. If it says 8 or 10 you should not experience said issue.

Set new value:

[root@localhost~]# echo 8 >  /sys/module/usbhid/parameters/mousepoll

And re-plug your mouse to apply the change.

Now interval between polling is set to 8 ms (125 times per second) and KSP will behave much better. I'm still in the search of method to change polling rate instantly and without raising my back from the chair.

Just thought: I can simply buy cheaper mouse. I'm pretty sure linux can have two mice connected at same time. Just swap them on the table when want to play KSP.

[ComradeWolfe]

Good morning all!

I recently made the jump from Windows to Mint 17.1 and had two questions as a Linux Noob. KSP is installed via Steam.

First, I tend to run CKAN but am tired of having to right-click to use Mono to open it. How does one go about making something like a script or windows .bat which I can just double-click?

Second, I'd like to run two installs. One for everyday, and one for stock-only challenges. I'm not 100% sure how to go about this -- do I just copy the game folder from my Steam directory to an arbitrary other folder? If so, what is the equivalent to Windows' "Program Files" folder?

Feel free to link to tutorials if such exist. Also, I will not feel at all patronized if you dumb things down for me. As a life-long Windows power-user, learning Linux has made me feel like an old person taking lessons in "email" or "Facebook" at a senior center.

Edited August 26, 2015 by ComradeWolfe
Missed a line break. Questions don't end in periods.

[sal_vager]

Hmm, maybe something like this.

Make a new text file in Gedit or similar, and add this, changing the path to your copy of KSP.

#! /bin/sh
cd "/home/yourusernam/.steam/steamapps/common/Kerbal Space Program/"
mono ckan.exe

Save it and make it executable, you can do this in the right click menu for the file as well.

To "install" another copy of KSP just copy your KSP folder anywhere you like in your home folder and it'll work, I have put mine in /home/me/games/KSP

The /usr folder is roughly equivalent to C:\Program Files, but it's best left alone and only stuff you install via the package manager will go there.

Edited August 26, 2015 by sal_vager

[ComradeWolfe]

Thanks a bunch.

I'll try it when I get home from work.

// I'm too used to calling out a program by name, then adding a file as an argument after the fact.

// Calling mono without explicitly telling the OS that it's a program/location seems kind of funky.

// Linux == Funky ... I'm down with that.

[steve_v]

binfmt_misc / filetype magic should take care of the "open with mono" bit. As such, you should be able to simply execute the binary as if it was native.

Any binary in your $PATH environment variable (e.g. stuff in /usr/bin/) can be invoked by name from anywhere, otherwise needs full path on the command line. Shorthand for the current working directory is './', so './ckan.exe' should work just like 'mono ckan.exe' or '/usr/bin/mono ./ckan.exe'.

As far as "Program files", there is no equivalent. *nix locates files by function not by package, so all binaries go in e.g. /usr/bin/ and all libraries in /usr/lib/, regardless of what software package they belong to. See the Filesystem Hierarchy Standard for details.

---more "on topic"---

This "double clicking" thing everybody seems so enamoured with... It depends on your desktop environment.

If you're using GNOME/MATE/Nautilus (I think that's what Mint ships by default nowadays), IIRC there's something like "Allow executing file as program" in the properties tab for the script in question, or "Run executable text files" somewhere in Edit -> Preferences menu.

I run KDE mostly, but haven't actually bothered figuring this out myself, I just have "alias ksp='cd ~/Games/KSP_linux; ./KSP.x86_64'" in my ~/.bash_aliases, so I can enter "ksp" in a terminal to start the game. Likewise for ckan.

Edited August 27, 2015 by steve_v

[ebigunso]

I've finally gotten around to doing what you guys told me to do. Sorry for being this late.

Plz check on page 44-46 if you forgot what my issue was.

So I've gone and ran the dmesg command after unplugging and replugging the HDD. Here is what I got.

I think the last 15 lines is related, but still I posted the whole output (who knows if I'm wrong).

[    2.667813] Console: switching to colour frame buffer device 128x48
[    2.668931] fb0: EFI VGA frame buffer device
[    2.668939] intel_idle: MWAIT substates: 0x42120
[    2.668940] intel_idle: v0.4 model 0x3C
[    2.668941] intel_idle: lapic_timer_reliable_states 0xffffffff
[    2.669156] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[    2.669159] ACPI: Power Button [PWRB]
[    2.669180] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    2.669181] ACPI: Power Button [PWRF]
[    2.669215] ACPI: Fan [FAN0] (off)
[    2.669229] ACPI: Fan [FAN1] (off)
[    2.669243] ACPI: Fan [FAN2] (off)
[    2.669256] ACPI: Fan [FAN3] (off)
[    2.669269] ACPI: Fan [FAN4] (off)
[    2.669569] thermal LNXTHERM:00: registered as thermal_zone0
[    2.669570] ACPI: Thermal Zone [TZ00] (28 C)
[    2.669683] thermal LNXTHERM:01: registered as thermal_zone1
[    2.669684] ACPI: Thermal Zone [TZ01] (30 C)
[    2.669709] GHES: HEST is not enabled!
[    2.669770] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    2.690133] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    2.691008] serial 0000:00:16.3: enabling device (0000 -> 0003)
[    2.711191] 0000:00:16.3: ttyS4 at I/O 0xf0c0 (irq = 19, base_baud = 115200) is a 16550A
[    2.711345] Linux agpgart interface v0.103
[    2.712096] brd: module loaded
[    2.712457] loop: module loaded
[    2.712589] libphy: Fixed MDIO Bus: probed
[    2.712591] tun: Universal TUN/TAP device driver, 1.6
[    2.712591] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[    2.712622] PPP generic driver version 2.4.2
[    2.712649] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.712652] ehci-pci: EHCI PCI platform driver
[    2.712708] ehci-pci 0000:00:1a.0: EHCI Host Controller
[    2.712711] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[    2.712721] ehci-pci 0000:00:1a.0: debug port 2
[    2.716613] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[    2.716622] ehci-pci 0000:00:1a.0: irq 16, io mem 0xdb91c000
[    2.726319] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[    2.726341] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.726342] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.726343] usb usb1: Product: EHCI Host Controller
[    2.726343] usb usb1: Manufacturer: Linux 3.16.0-30-generic ehci_hcd
[    2.726344] usb usb1: SerialNumber: 0000:00:1a.0
[    2.726419] hub 1-0:1.0: USB hub found
[    2.726422] hub 1-0:1.0: 2 ports detected
[    2.726528] ehci-pci 0000:00:1d.0: EHCI Host Controller
[    2.726530] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    2.726539] ehci-pci 0000:00:1d.0: debug port 2
[    2.730443] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[    2.730450] ehci-pci 0000:00:1d.0: irq 23, io mem 0xdb91b000
[    2.742313] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    2.742340] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    2.742341] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.742341] usb usb2: Product: EHCI Host Controller
[    2.742342] usb usb2: Manufacturer: Linux 3.16.0-30-generic ehci_hcd
[    2.742343] usb usb2: SerialNumber: 0000:00:1d.0
[    2.742438] hub 2-0:1.0: USB hub found
[    2.742441] hub 2-0:1.0: 2 ports detected
[    2.742504] ehci-platform: EHCI generic platform driver
[    2.742510] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.742513] ohci-pci: OHCI PCI platform driver
[    2.742519] ohci-platform: OHCI generic platform driver
[    2.742524] uhci_hcd: USB Universal Host Controller Interface driver
[    2.742579] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    2.742582] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    2.742649] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    2.742660] xhci_hcd 0000:00:14.0: irq 46 for MSI/MSI-X
[    2.742718] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.742719] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.742719] usb usb3: Product: xHCI Host Controller
[    2.742720] usb usb3: Manufacturer: Linux 3.16.0-30-generic xhci_hcd
[    2.742721] usb usb3: SerialNumber: 0000:00:14.0
[    2.742779] hub 3-0:1.0: USB hub found
[    2.742792] hub 3-0:1.0: 14 ports detected
[    2.744061] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    2.744064] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[    2.744084] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.744084] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.744085] usb usb4: Product: xHCI Host Controller
[    2.744086] usb usb4: Manufacturer: Linux 3.16.0-30-generic xhci_hcd
[    2.744087] usb usb4: SerialNumber: 0000:00:14.0
[    2.744143] hub 4-0:1.0: USB hub found
[    2.744152] hub 4-0:1.0: 6 ports detected
[    2.744740] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    2.745122] serio: i8042 KBD port at 0x60,0x64 irq 1
[    2.745126] serio: i8042 AUX port at 0x60,0x64 irq 12
[    2.745213] mousedev: PS/2 mouse device common for all mice
[    2.745321] rtc_cmos 00:02: RTC can wake from S4
[    2.745415] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
[    2.745437] rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    2.745493] device-mapper: uevent: version 1.0.3
[    2.745529] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: [email protected]
[    2.745537] Intel P-state driver initializing.
[    2.745563] Intel pstate controlling: cpu 0
[    2.745572] Intel pstate controlling: cpu 1
[    2.745595] Intel pstate controlling: cpu 2
[    2.745605] Intel pstate controlling: cpu 3
[    2.745632] Intel pstate controlling: cpu 4
[    2.745643] Intel pstate controlling: cpu 5
[    2.745665] Intel pstate controlling: cpu 6
[    2.745674] Intel pstate controlling: cpu 7
[    2.745701] Consider also installing thermald for improved thermal control.
[    2.745704] ledtrig-cpu: registered to indicate activity on CPUs
[    2.745708] EFI Variables Facility v0.08 2004-May-17
[    2.748522] TCP: cubic registered
[    2.748576] NET: Registered protocol family 10
[    2.748804] NET: Registered protocol family 17
[    2.748810] Key type dns_resolver registered
[    2.749343] Loading compiled-in X.509 certificates
[    2.749805] Loaded X.509 cert 'Magrathea: Glacier signing key: 7be2a7200f17f00ca011f70e5a874c37e3e0f6be'
[    2.749812] registered taskstats version 1
[    2.751456] Key type trusted registered
[    2.752900] Key type encrypted registered
[    2.754213] AppArmor: AppArmor sha1 policy hashing enabled
[    2.754216] ima: No TPM chip found, activating TPM-bypass!
[    2.754236] evm: HMAC attrs: 0x1
[    2.754853]   Magic number: 11:871:709
[    2.754963] rtc_cmos 00:02: setting system clock to 2015-08-29 00:44:44 UTC (1440809084)
[    2.755097] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    2.755098] EDD information not available.
[    2.755155] PM: Hibernation image not present or could not be loaded.
[    2.755662] Freeing unused kernel memory: 1356K (ffffffff82d1c000 - ffffffff82e6f000)
[    2.755663] Write protecting the kernel read-only data: 12288k
[    2.756673] Freeing unused kernel memory: 564K (ffff880002773000 - ffff880002800000)
[    2.757462] Freeing unused kernel memory: 500K (ffff880002b83000 - ffff880002c00000)
[    2.764557] systemd-udevd[149]: starting version 204
[    2.780145] [drm] Initialized drm 1.1.0 20060810
[    2.780657] ahci 0000:00:1f.2: version 3.0
[    2.780769] ahci 0000:00:1f.2: irq 47 for MSI/MSI-X
[    2.780819] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x33 impl SATA mode
[    2.780822] ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part ems apst 
[    2.783269] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    2.783274] r8169 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
[    2.783498] r8169 0000:06:00.0: irq 48 for MSI/MSI-X
[    2.783615] wmi: Mapper loaded
[    2.783687] r8169 0000:06:00.0 eth0: RTL8168evl/8111evl at 0xffffc90005b9e000, 74:d4:35:16:a0:47, XID 0c900800 IRQ 48
[    2.783689] r8169 0000:06:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    2.796870] checking generic (d9000000 300000) vs hw (d0000000 8000000)
[    2.796872] checking generic (d9000000 300000) vs hw (d8000000 2000000)
[    2.796872] fb: switching to nouveaufb from EFI VGA
[    2.796884] Console: switching to colour dummy device 80x25
[    2.797140] nouveau  [  DEVICE][0000:03:00.0] BOOT0  : 0x0e4080a2
[    2.797142] nouveau  [  DEVICE][0000:03:00.0] Chipset: GK104 (NVE4)
[    2.797143] nouveau  [  DEVICE][0000:03:00.0] Family : NVE0
[    2.797157] nouveau  [   VBIOS][0000:03:00.0] checking PRAMIN for image...
[    2.797163] nouveau  [   VBIOS][0000:03:00.0] ... signature not found
[    2.797164] nouveau  [   VBIOS][0000:03:00.0] checking PROM for image...
[    2.802985] scsi0 : ahci
[    2.803216] scsi1 : ahci
[    2.803436] scsi2 : ahci
[    2.803621] scsi3 : ahci
[    2.803838] scsi4 : ahci
[    2.804053] scsi5 : ahci
[    2.804086] ata1: SATA max UDMA/133 abar m2048@0xdb91a000 port 0xdb91a100 irq 47
[    2.804089] ata2: SATA max UDMA/133 abar m2048@0xdb91a000 port 0xdb91a180 irq 47
[    2.804089] ata3: DUMMY
[    2.804090] ata4: DUMMY
[    2.804093] ata5: SATA max UDMA/133 abar m2048@0xdb91a000 port 0xdb91a300 irq 47
[    2.804097] ata6: SATA max UDMA/133 abar m2048@0xdb91a000 port 0xdb91a380 irq 47
[    2.804199] i915 0000:00:02.0: enabling device (0006 -> 0007)
[    2.834355] nouveau  [   VBIOS][0000:03:00.0] ... appears to be valid
[    2.834356] nouveau  [   VBIOS][0000:03:00.0] using image from PROM
[    2.834419] nouveau  [   VBIOS][0000:03:00.0] BIT signature found
[    2.834420] nouveau  [   VBIOS][0000:03:00.0] version 80.04.1e.00.13
[    2.834650] nouveau 0000:03:00.0: irq 49 for MSI/MSI-X
[    2.834657] nouveau  [     PMC][0000:03:00.0] MSI interrupts enabled
[    2.834689] nouveau  [     PFB][0000:03:00.0] RAM type: GDDR5
[    2.834690] nouveau  [     PFB][0000:03:00.0] RAM size: 2048 MiB
[    2.834691] nouveau  [     PFB][0000:03:00.0]    ZCOMP: 0 tags
[    2.836962] nouveau  [    VOLT][0000:03:00.0] GPU voltage: 987500uv
[    2.865468] nouveau  [  PTHERM][0000:03:00.0] FAN control: PWM
[    2.865475] nouveau  [  PTHERM][0000:03:00.0] fan management: automatic
[    2.865493] nouveau  [  PTHERM][0000:03:00.0] internal sensor: yes
[    2.865521] nouveau  [     CLK][0000:03:00.0] 07: core 324 MHz memory 648 MHz 
[    2.865540] nouveau  [     CLK][0000:03:00.0] 0a: core 324-862 MHz memory 1620 MHz 
[    2.865591] nouveau  [     CLK][0000:03:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
[    2.865655] nouveau  [     CLK][0000:03:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
[    2.865734] nouveau  [     CLK][0000:03:00.0] --: core 324 MHz memory 648 MHz 
[    2.895189] [TTM] Zone  kernel: Available graphics memory: 8154876 kiB
[    2.895190] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    2.895191] [TTM] Initializing pool allocator
[    2.895193] [TTM] Initializing DMA pool allocator
[    2.895198] nouveau  [     DRM] VRAM: 2048 MiB
[    2.895199] nouveau  [     DRM] GART: 1048576 MiB
[    2.895200] nouveau  [     DRM] TMDS table version 2.0
[    2.895201] nouveau  [     DRM] DCB version 4.0
[    2.895202] nouveau  [     DRM] DCB outp 00: 02000f00 00000000
[    2.895203] nouveau  [     DRM] DCB outp 01: 01020f02 00020030
[    2.895203] nouveau  [     DRM] DCB outp 02: 08011f82 00020030
[    2.895204] nouveau  [     DRM] DCB outp 03: 04832fb6 0f420010
[    2.895205] nouveau  [     DRM] DCB outp 04: 04032f72 00020010
[    2.895205] nouveau  [     DRM] DCB conn 00: 00001030
[    2.895206] nouveau  [     DRM] DCB conn 01: 01000131
[    2.895207] nouveau  [     DRM] DCB conn 02: 00020246
[    2.896144] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.896144] [drm] Driver supports precise vblank timestamp query.
[    2.901609] nouveau  [     DRM] MM: using COPY for buffer copies
[    3.038487] usb 1-1: new high-speed USB device number 2 using ehci-pci
[    3.117516] nouveau  [     DRM] allocated 1920x1080 fb: 0x80000, bo ffff880437a80400
[    3.117614] fbcon: nouveaufb (fb0) is primary device
[    3.122513] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.122537] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.122569] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    3.123447] ata2.00: ATA-8: WDC WD10EZEX-00RKKA0, 80.00A80, max UDMA/133
[    3.123448] ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    3.124640] ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    3.124641] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    3.124642] ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    3.125334] ata2.00: configured for UDMA/133
[    3.126198] ata6.00: ATAPI: ATAPI   iHAS324   W, HL18, max UDMA/100
[    3.126487] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.127517] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    3.127518] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    3.127518] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    3.128622] ata5.00: ATA-8: Hitachi HDT721010SLA360, ST6OA3AA, max UDMA/133
[    3.128622] ata5.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    3.129051] ata6.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    3.129051] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    3.129052] ata6.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    3.129828] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[    3.129829] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[    3.129830] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[    3.130603] ata6.00: configured for UDMA/100
[    3.130912] ata5.00: configured for UDMA/133
[    3.170877] usb 1-1: New USB device found, idVendor=8087, idProduct=8008
[    3.170878] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.171181] hub 1-1:1.0: USB hub found
[    3.171293] hub 1-1:1.0: 6 ports detected
[    3.200860] ata1.00: ATA-8: TOSHIBA MK1002TSKB, MT4A, max UDMA/100
[    3.200860] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    3.201450] ata1.00: configured for UDMA/100
[    3.201601] scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MK1002TS MT4A PQ: 0 ANSI: 5
[    3.201841] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.201864] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    3.201867] sd 0:0:0:0: [sda] Write Protect is off
[    3.201882] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.201895] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.202004] scsi 1:0:0:0: Direct-Access     ATA      WDC WD10EZEX-00R 0A80 PQ: 0 ANSI: 5
[    3.202194] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    3.202200] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.202201] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[    3.202356] scsi 4:0:0:0: Direct-Access     ATA      Hitachi HDT72101 A3AA PQ: 0 ANSI: 5
[    3.202396] sd 1:0:0:0: [sdb] Write Protect is off
[    3.202397] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.202428] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.202563] sd 4:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[    3.202582] sd 4:0:0:0: Attached scsi generic sg2 type 0
[    3.202639] sd 4:0:0:0: [sdc] Write Protect is off
[    3.202640] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    3.202679] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.203041] scsi 5:0:0:0: CD-ROM            ATAPI    iHAS324   W      HL18 PQ: 0 ANSI: 5
[    3.214620] sr0: scsi3-mmc drive: 125x/125x writer dvd-ram cd/rw xa/form2 cdda tray
[    3.214621] cdrom: Uniform CD-ROM driver Revision: 3.20
[    3.214709] sr 5:0:0:0: Attached scsi CD-ROM sr0
[    3.214767] sr 5:0:0:0: Attached scsi generic sg3 type 5
[    3.215519]  sdc: sdc1
[    3.216083] sd 4:0:0:0: [sdc] Attached SCSI disk
[    3.225874]  sdb: sdb1 sdb2
[    3.226403] sd 1:0:0:0: [sdb] Attached SCSI disk
[    3.282570] usb 2-1: new high-speed USB device number 2 using ehci-pci
[    3.335410]  sda: sda1
[    3.335537] sd 0:0:0:0: [sda] Attached SCSI disk
[    3.353213] Console: switching to colour frame buffer device 240x67
[    3.354475] nouveau 0000:03:00.0: fb0: nouveaufb frame buffer device
[    3.354476] nouveau 0000:03:00.0: registered panic notifier
[    3.362614] [drm] Initialized nouveau 1.1.2 20120801 for 0000:03:00.0 on minor 0
[    3.362645] nouveau 0000:04:00.0: enabling device (0004 -> 0007)
[    3.362932] [drm] Memory usable by graphics device = 2048M
[    3.362934] [drm] Replacing VGA console driver
[    3.386742] i915 0000:00:02.0: irq 50 for MSI/MSI-X
[    3.386748] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.386749] [drm] Driver supports precise vblank timestamp query.
[    3.386762] vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=none:owns=none
[    3.386763] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns=none
[    3.414988] usb 2-1: New USB device found, idVendor=8087, idProduct=8000
[    3.414989] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.415304] hub 2-1:1.0: USB hub found
[    3.415461] hub 2-1:1.0: 8 ports detected
[    3.582701] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[    3.611585] i915 0000:00:02.0: No connectors reported connected with modes
[    3.611587] [drm] Cannot find any crtc or sizes - going 1024x768
[    3.611877] i915 0000:00:02.0: fb1: inteldrmfb frame buffer device
[    3.615363] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    3.615597] acpi device:62: registered as cooling_device13
[    3.615659] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[    3.615800] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 1
[    3.616050] nouveau  [  DEVICE][0000:04:00.0] BOOT0  : 0x0e4080a2
[    3.616052] nouveau  [  DEVICE][0000:04:00.0] Chipset: GK104 (NVE4)
[    3.616053] nouveau  [  DEVICE][0000:04:00.0] Family : NVE0
[    3.616094] nouveau  [   VBIOS][0000:04:00.0] checking PRAMIN for image...
[    3.616103] nouveau  [   VBIOS][0000:04:00.0] ... signature not found
[    3.616104] nouveau  [   VBIOS][0000:04:00.0] checking PROM for image...
[    3.662733] tsc: Refined TSC clocksource calibration: 3392.138 MHz
[    3.668070] nouveau  [   VBIOS][0000:04:00.0] ... appears to be valid
[    3.668072] nouveau  [   VBIOS][0000:04:00.0] using image from PROM
[    3.668123] nouveau  [   VBIOS][0000:04:00.0] BIT signature found
[    3.668124] nouveau  [   VBIOS][0000:04:00.0] version 80.04.1e.00.14
[    3.668284] nouveau  [ DEVINIT][0000:04:00.0] adaptor not initialised
[    3.668292] nouveau  [   VBIOS][0000:04:00.0] running init tables
[    3.712307] usb 3-1: New USB device found, idVendor=05ac, idProduct=12a8
[    3.712309] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.712310] usb 3-1: Product: iPhone
[    3.712311] usb 3-1: Manufacturer: Apple Inc.
[    3.712311] usb 3-1: SerialNumber: a1b6cedd13348a6ad613971316eb8b03e41cb518
[    3.712433] usb 3-1: ep 0x2 - rounding interval to 8 microframes, ep desc says 10 microframes
[    3.712436] usb 3-1: ep 0x81 - rounding interval to 8 microframes, ep desc says 10 microframes
[    3.718984] random: nonblocking pool is initialized
[    3.870718] nouveau 0000:04:00.0: irq 51 for MSI/MSI-X
[    3.870726] nouveau  [     PMC][0000:04:00.0] MSI interrupts enabled
[    3.870761] nouveau  [     PFB][0000:04:00.0] RAM type: GDDR5
[    3.870762] nouveau  [     PFB][0000:04:00.0] RAM size: 2048 MiB
[    3.870763] nouveau  [     PFB][0000:04:00.0]    ZCOMP: 0 tags
[    3.873018] nouveau  [    VOLT][0000:04:00.0] GPU voltage: 987500uv
[    3.878860] usb 3-3: new full-speed USB device number 3 using xhci_hcd
[    3.901542] nouveau  [  PTHERM][0000:04:00.0] FAN control: PWM
[    3.901550] nouveau  [  PTHERM][0000:04:00.0] fan management: automatic
[    3.901568] nouveau  [  PTHERM][0000:04:00.0] internal sensor: yes
[    3.901596] nouveau  [     CLK][0000:04:00.0] 07: core 324 MHz memory 648 MHz 
[    3.901616] nouveau  [     CLK][0000:04:00.0] 0a: core 324-862 MHz memory 1620 MHz 
[    3.901670] nouveau  [     CLK][0000:04:00.0] 0d: core 540-1202 MHz memory 6008 MHz 
[    3.901734] nouveau  [     CLK][0000:04:00.0] 0f: core 540-1202 MHz memory 6008 MHz 
[    3.901813] nouveau  [     CLK][0000:04:00.0] --: core 324 MHz memory 648 MHz 
[    3.930834] nouveau  [     DRM] VRAM: 2048 MiB
[    3.930834] nouveau  [     DRM] GART: 1048576 MiB
[    3.930836] nouveau  [     DRM] TMDS table version 2.0
[    3.930837] nouveau  [     DRM] DCB version 4.0
[    3.930838] nouveau  [     DRM] DCB outp 00: 02000f00 00000000
[    3.930839] nouveau  [     DRM] DCB outp 01: 01020f02 00020030
[    3.930840] nouveau  [     DRM] DCB conn 00: 00001030
[    3.931704] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.931704] [drm] Driver supports precise vblank timestamp query.
[    3.937191] nouveau  [     DRM] MM: using COPY for buffer copies
[    3.937197] [drm] Initialized nouveau 1.1.2 20120801 for 0000:04:00.0 on minor 2
[    4.007992] usb 3-3: New USB device found, idVendor=131d, idProduct=0158
[    4.007993] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.174951] usb 3-6: new high-speed USB device number 4 using xhci_hcd
[    4.304125] usb 3-6: New USB device found, idVendor=05e3, idProduct=0608
[    4.304127] usb 3-6: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    4.304128] usb 3-6: Product: USB2.0 Hub
[    4.304841] hub 3-6:1.0: USB hub found
[    4.305133] hub 3-6:1.0: 4 ports detected
[    4.471103] usb 3-10: new high-speed USB device number 5 using xhci_hcd
[    4.663395] Switched to clocksource tsc
[    4.827247] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[    5.539609] ISO 9660 Extensions: Microsoft Joliet Level 3
[    5.541763] ISO 9660 Extensions: RRIP_1991A
[    5.714223] usb 3-10: New USB device found, idVendor=046d, idProduct=082d
[    5.714224] usb 3-10: New USB device strings: Mfr=0, Product=2, SerialNumber=1
[    5.714225] usb 3-10: Product: HD Pro Webcam C920
[    5.714226] usb 3-10: SerialNumber: 47CCC2FF
[    5.821755] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    5.879665] usb 3-12: new full-speed USB device number 6 using xhci_hcd
[    6.114044] usb 3-12: New USB device found, idVendor=054c, idProduct=0268
[    6.114045] usb 3-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.114046] usb 3-12: Product: PLAYSTATION(R)3 Controller
[    6.114047] usb 3-12: Manufacturer: Sony
[    6.117125] hidraw: raw HID events driver (C) Jiri Kosina
[    6.131252] usbcore: registered new interface driver usbhid
[    6.131253] usbhid: USB HID core driver
[    6.132818] sony 0003:054C:0268.0001: Fixing up Sony Sixaxis report descriptor
[    6.178805] input: Sony PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-12/3-12:1.0/0003:054C:0268.0001/input/input6
[    6.179048] sony 0003:054C:0268.0001: input,hiddev0,hidraw0: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-0000:00:14.0-12/input0
[    6.224010] usb 4-5: new SuperSpeed USB device number 2 using xhci_hcd
[    6.240587] usb 4-5: New USB device found, idVendor=0411, idProduct=0227
[    6.240589] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.240590] usb 4-5: Product: HD-LXVU3
[    6.240591] usb 4-5: Manufacturer: BUFFALO
[    6.240592] usb 4-5: SerialNumber: 0105B0006FEE
[    6.242562] usb-storage 4-5:1.0: USB Mass Storage device detected
[    6.242832] scsi6 : usb-storage 4-5:1.0
[    6.242888] usbcore: registered new interface driver usb-storage
[    6.243836] usbcore: registered new interface driver uas
[    6.312017] usb 3-6.2: new full-speed USB device number 7 using xhci_hcd
[    6.402767] usb 3-6.2: New USB device found, idVendor=046d, idProduct=c52b
[    6.402769] usb 3-6.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.402770] usb 3-6.2: Product: USB Receiver
[    6.402770] usb 3-6.2: Manufacturer: Logitech
[    6.409804] logitech-djreceiver 0003:046D:C52B.0004: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-6.2/input2
[    6.465520] input: Logitech Unifying Device. Wireless PID:101a as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6.2/3-6.2:1.2/0003:046D:C52B.0004/0003:046D:C52B.0005/input/input7
[    6.465721] logitech-djdevice 0003:046D:C52B.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101a] on usb-0000:00:14.0-6.2:1
[    6.480101] usb 3-6.3: new low-speed USB device number 8 using xhci_hcd
[    6.574444] usb 3-6.3: New USB device found, idVendor=046e, idProduct=5523
[    6.574445] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    6.574446] usb 3-6.3: Product: USB Device
[    6.574447] usb 3-6.3: Manufacturer: Device
[    6.574555] usb 3-6.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[    6.574557] usb 3-6.3: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
[    6.586395] input: Device USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6.3/3-6.3:1.0/0003:046E:5523.0006/input/input8
[    6.586450] hid-generic 0003:046E:5523.0006: input,hidraw3: USB HID v1.00 Keyboard [Device USB Device] on usb-0000:00:14.0-6.3/input0
[    6.586539] input: Device USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6.3/3-6.3:1.1/0003:046E:5523.0007/input/input9
[    6.586595] hid-generic 0003:046E:5523.0007: input,hidraw4: USB HID v1.00 Mouse [Device USB Device] on usb-0000:00:14.0-6.3/input1
[    7.240423] scsi 6:0:0:0: CD-ROM            BUFFALO  Virtual Cdrom    0001 PQ: 0 ANSI: 6
[    7.241419] sr1: scsi-1 drive
[    7.241497] sr 6:0:0:0: Attached scsi CD-ROM sr1
[    7.241634] sr 6:0:0:0: Attached scsi generic sg4 type 5
[   29.952333] systemd-udevd[1242]: starting version 204
[   36.001086] parport_pc 00:06: reported by Plug and Play ACPI
[   36.001129] parport0: PC-style at 0x378, irq 5 [PCSPP,TRISTATE]
[   36.363005] lp0: using parport0 (interrupt-driven).
[   36.603487] ppdev: user-space parallel port driver
[   37.505969] init: cups main process (1314) killed by HUP signal
[   37.505974] init: cups main process ended, respawning
[   37.806242] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   38.828892] mei_me 0000:00:16.0: irq 52 for MSI/MSI-X
[   39.258756] AVX2 version of gcm_enc/dec engaged.
[   39.701076] Bluetooth: Core ver 2.19
[   39.701087] NET: Registered protocol family 31
[   39.701089] Bluetooth: HCI device and connection manager initialized
[   39.701094] Bluetooth: HCI socket layer initialized
[   39.701095] Bluetooth: L2CAP socket layer initialized
[   39.701101] Bluetooth: SCO socket layer initialized
[   40.913743] Bluetooth: RFCOMM TTY layer initialized
[   40.913750] Bluetooth: RFCOMM socket layer initialized
[   40.913753] Bluetooth: RFCOMM ver 1.11
[   41.363254] usb 3-1: ep 0x2 - rounding interval to 8 microframes, ep desc says 10 microframes
[   41.363258] usb 3-1: ep 0x81 - rounding interval to 8 microframes, ep desc says 10 microframes
[   41.473353] device-mapper: multipath: version 1.7.0 loaded
[   41.781756] media: Linux media interface: v0.10
[   41.912733] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   41.912735] Bluetooth: BNEP filters: protocol multicast
[   41.912741] Bluetooth: BNEP socket layer initialized
[   42.999357] init: failsafe main process (1543) killed by TERM signal
[   43.184355] Linux video capture interface: v2.00
[   44.749221] snd_hda_intel 0000:00:03.0: enabling device (0000 -> 0002)
[   44.749333] snd_hda_intel 0000:00:03.0: irq 53 for MSI/MSI-X
[   44.749370] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
[   44.749500] snd_hda_intel 0000:00:1b.0: irq 54 for MSI/MSI-X
[   44.749532] snd_hda_intel 0000:03:00.1: Disabling MSI
[   44.749546] snd_hda_intel 0000:03:00.1: Handle VGA-switcheroo audio client
[   44.749559] snd_hda_intel 0000:04:00.1: enabling device (0000 -> 0002)
[   44.749579] snd_hda_intel 0000:04:00.1: Disabling MSI
[   45.338830] usbcore: registered new interface driver snd-usb-audio
[   45.496017] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input10
[   45.496058] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input11
[   45.496193] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input12
[   45.628466] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:10.0/0000:04:00.1/sound/card3/input13
[   45.696785] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:08.0/0000:03:00.1/sound/card2/input14
[   45.696845] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:08.0/0000:03:00.1/sound/card2/input15
[   45.697542] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:08.0/0000:03:00.1/sound/card2/input16
[   46.413930] sound hdaudioC1D2: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[   46.413933] sound hdaudioC1D2:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   46.413934] sound hdaudioC1D2:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[   46.413934] sound hdaudioC1D2:    mono: mono_out=0x0
[   46.413935] sound hdaudioC1D2:    dig-out=0x11/0x0
[   46.413936] sound hdaudioC1D2:    inputs:
[   46.413937] sound hdaudioC1D2:      Front Mic=0x19
[   46.413938] sound hdaudioC1D2:      Rear Mic=0x18
[   46.413939] sound hdaudioC1D2:      Line=0x1a
[   46.413940] sound hdaudioC1D2:    dig-in=0x1f
[   46.425622] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input17
[   46.425681] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input18
[   46.425752] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card1/input19
[   46.425818] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card1/input20
[   46.425890] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card1/input21
[   46.425973] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card1/input22
[   46.426057] input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1b.0/sound/card1/input23
[   46.426133] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input24
[   46.780137] intel_rapl: Found RAPL domain package
[   46.780140] intel_rapl: Found RAPL domain core
[   46.780142] intel_rapl: Found RAPL domain uncore
[   46.780144] intel_rapl: Found RAPL domain dram
[   47.936685] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
[   47.937120] input: HD Pro Webcam C920 as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.0/input/input25
[   47.937172] usbcore: registered new interface driver uvcvideo
[   47.937173] USB Video Class driver (1.1.1)
[   52.969238] ipheth 3-1:4.2: Apple iPhone USB Ethernet device attached
[   52.969261] usbcore: registered new interface driver ipheth
[   58.728428] init: alsa-restore main process (1834) terminated with status 99
[   60.037152] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   60.276409] r8169 0000:06:00.0 eth0: link down
[   60.276459] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   60.276479] r8169 0000:06:00.0 eth0: link down
[   61.854666] r8169 0000:06:00.0 eth0: link up
[   61.854671] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   72.720026] init: plymouth-upstart-bridge main process ended, respawning
[   72.723621] init: plymouth-upstart-bridge main process (2648) terminated with status 1
[   72.723638] init: plymouth-upstart-bridge main process ended, respawning
[  116.697697] sound hdaudioC2D0: hda-codec: out of range cmd 0:4:707:ffffffff
[  118.002228] sound hdaudioC3D0: hda-codec: out of range cmd 0:4:707:ffffffbf
[  132.674921] ISO 9660 Extensions: Microsoft Joliet Level 3
[  132.675091] ISOFS: changing to secondary root
[  163.408854] systemd-hostnamed[4110]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[  642.748569] usb 4-5: USB disconnect, device number 2
[  659.791600] usb 4-5: new SuperSpeed USB device number 3 using xhci_hcd
[  659.808163] usb 4-5: New USB device found, idVendor=0411, idProduct=0227
[  659.808165] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  659.808166] usb 4-5: Product: HD-LXVU3
[  659.808166] usb 4-5: Manufacturer: BUFFALO
[  659.808167] usb 4-5: SerialNumber: 0105B0006FEE
[  659.808586] usb-storage 4-5:1.0: USB Mass Storage device detected
[  659.808812] scsi7 : usb-storage 4-5:1.0
[  660.808134] scsi 7:0:0:0: CD-ROM            BUFFALO  Virtual Cdrom    0001 PQ: 0 ANSI: 6
[  660.809505] sr1: scsi-1 drive
[  660.809630] sr 7:0:0:0: Attached scsi CD-ROM sr1
[  660.809684] sr 7:0:0:0: Attached scsi generic sg4 type 5
[  660.926772] ISO 9660 Extensions: Microsoft Joliet Level 3
[  660.926940] ISOFS: changing to secondary root
ubuntu@ubuntu:~$ 

I also went back into the BIOS to check on the boot settings once again, and to also check the names of where I was talking about before.

First of all, my BIOS is a "Gigabyte UFEI DualBIOS" or at least thats what it said on screen. Mode name was H87-HD3.

I've rechecked what the column name was for the place I said I configured to HDD, and that was:

Under the Periperals tab, Below the line which saids "USB Storage Devices" in white, a setting named "BUFFALO Virtual Cdrom 0001".

The settings that were there was, from the top, "Auto" "Floppy" "Forced FDD" "Hard Disk" and "CD-ROM".

Changing the setting here from Auto to Hard Disk didn't help in resolving the issue.

Now on to the boot settings, I've checked the boot HDD list (boot priority setting) and the drive I'm after was not listed there. So I tried looking into the "CD/DVD Rom drive BBS Properties" insted of the HDD one, and wolla it was there. The name written there was "BUFFALO Virtual Cdrom 0001".

So I've now found out that the disk is recognized as a CDROM device at bios level.

The thing I specified is different from my actual CDROM drive, btw. That was also there in the list so I'm not confusing that for the HDD in question.

What ever advice I can get to reslove this issue is very appriciated.

My goal is to make this damn thing get recognized as an HDD when I boot into Ubuntu from my installation disk.

Edited August 28, 2015 by ebigunso

[sal_vager]

It appears the drive has a hidden partition containing the device driver, and because this partition is an optical disk format (Microsoft Joliet Level 3, ISO 9660) and is likely the first partition on the device it identifies as a cdrom.

I have run into issues in the distant past with hidden partitions also making any partitions after them inaccessible.

Hidden partitions are tricky to remove, but a guy here managed it in Windows and it should be possible to delete the MBR of the usb drive in gParted.

It may also be possible to delete the partition in Gnome disk utility by clicking the gears icon when the usb drive is selected.

Also any version of partition magic will be able to unhide the hidden partition, allowing it to be deleted.

With that gone the bulk of the drive will be accessible and the partition can be enlarged in gParted, as you'd likely have around 700mb unused space.

[steve_v]

scsi 7:0:0:0: CD-ROM BUFFALO Virtual Cdrom 0001 PQ: 0 ANSI: 6

Ahh, so the device is lying to the OS, and the BIOS too it would seem.

This will make things interesting.

Does it actually appear as a normal HDD in Windoze, or are there special drivers on that "Virtual CDROM" to make it work?

I haven't seen one of these before, but I'll think on it. If there's no way to get it to present as a HDD you may be SOL though.

As Sal suggests, if you can get at the raw disk you may be able to nuke the MBR/partition table... assuming you can "see" the rest of the disk, potentially via the generic SCSI device node sg4.

The bit that concerns me is that there's no mention at all of the actual HDD, the "Virtual drive" may well be on flash rather than a simple partition on the HDD.

Can you confirm that both the WDC WD10EZEX-00R (sda) and Hitachi HDT72101 (sdb) 1 TB drives are real, and neither of them are the external enclosure? Edit: Nevermind, reading back through the thread it's a 4TB disk, so that's not it.

Everything I have seen so far of this type of device indicates there should be a second device associated with the HDD itself, since it's not there the disk may well have hardware issues. Can you confirm it works on a Windows machine?

Still snouting about for more info on how this thing is meant to work...

- - - Updated - - -

A random thought has struck my brain... How is the device powered?

Does it require external power, is it plugged in (sorry, had to ask ) and can you feel/hear the disk spin up?

If it doesn't, and it has no external power, have you a powered hub to connect it to?

Edited August 29, 2015 by steve_v

[ebigunso]

It appears the drive has a hidden partition containing the device driver, and because this partition is an optical disk format (Microsoft Joliet Level 3, ISO 9660) and is likely the first partition on the device it identifies as a cdrom.

I have run into issues in the distant past with hidden partitions also making any partitions after them inaccessible.

Hidden partitions are tricky to remove, but a guy here managed it in Windows and it should be possible to delete the MBR of the usb drive in gParted.

It may also be possible to delete the partition in Gnome disk utility by clicking the gears icon when the usb drive is selected.

Also any version of partition magic will be able to unhide the hidden partition, allowing it to be deleted.

With that gone the bulk of the drive will be accessible and the partition can be enlarged in gParted, as you'd likely have around 700mb unused space.

Ahh, so the device is lying to the OS, and the BIOS too it would seem.

This will make things interesting.

Does it actually appear as a normal HDD in Windoze, or are there special drivers on that "Virtual CDROM" to make it work?

I haven't seen one of these before, but I'll think on it. If there's no way to get it to present as a HDD you may be SOL though.

As Sal suggests, if you can get at the raw disk you may be able to nuke the MBR/partition table... assuming you can "see" the rest of the disk, potentially via the generic SCSI device node sg4.

The bit that concerns me is that there's no mention at all of the actual HDD, the "Virtual drive" may well be on flash rather than a simple partition on the HDD.

Can you confirm that both the WDC WD10EZEX-00R (sda) and Hitachi HDT72101 (sdb) 1 TB drives are real, and neither of them are the external enclosure? Edit: Nevermind, reading back through the thread it's a 4TB disk, so that's not it.

Everything I have seen so far of this type of device indicates there should be a second device associated with the HDD itself, since it's not there the disk may well have hardware issues. Can you confirm it works on a Windows machine?

Still snouting about for more info on how this thing is meant to work...

- - - Updated - - -

A random thought has struck my brain... How is the device powered?

Does it require external power, is it plugged in (sorry, had to ask ) and can you feel/hear the disk spin up?

If it doesn't, and it has no external power, have you a powered hub to connect it to?

Alright, so I went on and used the "HP USB Disk Storage Format Tool" like is written in the link sal gave me. It gave me an error saying the disk is read only (weird), but it still did nuke the partition and made the whole disk appear as an unallocated partition. So I went on to reformatting it to a single NTFS partition + some free space to put Ubuntu into. This is all from inside Windows so I'll check what it looks like from Ubuntu later on.

This device shows up the same way as any other HDD I have on my PC, inside the My Computer directory. Pic here.

Drive labeled (H: ) is the one. As you probably can see from the disk space.

Just as a side note, those autorun.inf and all that thingies that was visible from Ubuntu was hidden when viewed from Windows. So I'll have to check again from Ubuntu to see if it actually did get nuked.

Regarding how the device is powered, it has a dedicated power input which takes from a power socket.

When I disconnect the USB connection with the PC (not power but USB) then reconnect, I can hear it spin up. This disk has a cooling fan so I can hear that start spinning too.

Also there's a sort of an access lamp in the front side of this device, which doesn't light when not connected, lights up red when it is connected but not in windows (I think this means it's not fully operational at this point?), and when in Windows and in working condition it goes to blue.

Edited August 31, 2015 by ebigunso

[steve_v]

So I went on to reformatting it to a single NTFS partition + some free space to put Ubuntu into. This is all from inside Windows so I'll check what it looks like from Ubuntu later on.

This sounds exceedingly promising

[ebigunso]

OK so now I went into Ubuntu to check. Unfortunately, the disk seems to have not been nuked since it still has the same files inside and has the same problem of showing up as CDROM.

I suspect this is due to that error message from "HP USB Disk Storage Format Tool" that said the disk is write protected.

Now if I can find a way to remove this protection, I think that would move me ahead a step.

- - - Updated - - -

I've tried removing write protection of the disk via diskpart and the command "attribute disk clear readonly" with admin permissions but it didn't work. The format tool still gives me the error when I run it. Seems I need to find another way to do this.

[WolfgangAxel]

Hello to all!

A little backstory- Thanks to this thread, I got KSP working on CrunchBang Linux a few months ago (it's basically OpenBox Debian with some user-friendly configs pre-installed). I don't know if it was my bias towards Linux over Windows, but I felt like the game ran slightly faster (when it didn't crash). I tried updating my fglrx drivers from AMD's website, but something went awry and really messed up my video drivers altogether. I figured since CrunchBang got abandoned, I'd just wipe my Linux half and install Bunsen rather than fight to understand what went wrong (Bunsen is essentially a clone of CB, only alive and not dead). I've been slowly reconfiguring my laptop to be roughly what it was, which meant getting KSP working. With a bit of fighting I got all the 32bit libs and eventually got the game to boot fine. After I saw the menu screen, I considered it a victory and went to bed.

I'm not sure what exactly broke the game, but after fixing a few unfufilled mod dependencies, my game would load completely and crash just before leaving the progress bar screen. I checked the log file, and there weren't any errors listed. The last two entries listed were

The SpaceNavigator driver is a Windows-Only feature at the moment.
Agent: Found 19 agent mentality types

which doesn't look like an error to me. I ran it in a terminal, and the only sign of error it gave me was a single "Aborted" when it crashed.

I thought I remembered reading that KSP didn't run on kernels before a certain era, so I checked out what Bunsen had installed. It was using 3.16.0, which I figured was probably before that point, if it exists. I upgraded the kernel to 4.2.0, and that's when it really got messy.

Now, when I try to launch either the x86 or x86_64 version, this is what my terminal pops out at me:

keaton@MissionControl:~/Documents/Kerbal Space Program$ LC_LANG=C ./KSP.x86_64
Set current directory to /home/keaton/Documents/Kerbal Space Program
Found path: /home/keaton/Documents/Kerbal Space Program/KSP.x86_64
Mono path[0] = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono/etc'
/dev/input/js0: driver version: 2.1.0 (20100)
          ---cut useless details about my xbox controller---
Aborted

The game aborts before it can create the KSP.log file, so I can't supply one for you to look at. I've tried using every variation of LC_LANG I've come across, and none of them change the output in the slightest. I completely deleted the modded install I was planning to play and replaced it with a fresh copy from my Steam folder, but still no dice.

I've been using Linux since 2009, so I'm no Linux newbie, but I'm not knowledgeable enough in computer science to know what broke. I'm sure updating the kernel to 4.2.0 made things worse, but I have no idea what nor why. Another thing that might be relevant is I installed the ibus-mozc package since the successful boot of the game, which may have messed with some locale settings? I'm not entirely sure.

Any insight is appreciated and thanks in advance!

[sal_vager]

Hi WolfgangAxel, first, good luck with Bunsen and congrats even getting this far, Unity officially supports Ubuntu 12.04.2 and up so should work with any kernel that version used and higher, and seeing the menu screen shows it will work.

I suggest testing without LC_LANG=C as it's only required if your system language swaps the comma and period, and if you upload the full Player.log and KSP.log I can see if there's anything I recognise.

[WolfgangAxel]

Thanks for the reply sal_vager!

Starting with only the ./KSP.x86 command, it still aborts immediately after "Mono config path = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono/etc' ". As for the .log files, the abort happens before the .log files are generated, so I don't have any to share with the current clean copy. Furthermore, I stupidly shift+deleted the entire KSP directory when it started reliably crashing at the progress bar, so I no longer have the .log files from the last time it got that far.

There is however a rogue KSP.log file in my home directory. I don't know exactly when along the span of errors it was generated, but the timestamp says yesterday at 7 PM. I had forgotten about needing to make a script that cd'd to the KSP directory, and had just launched the game by navigating to the executable that time. I'm positive that at that point I was running kernel 3.16.0. I remember the last .log I looked at went past where this one stops though; I know I closed KSP while it was still booting once yesterday, so this might be from that. I'm not hopeful that it will be very helpful.

When I have time tonight, I'm going to reinstall the 3.16.0 kernel and boot into that to see if I can at least get a progress bar crash again. I didn't make the connection last night that I did see it boot to the menu once, so the kernel wouldn't have been the culprit. If it works, I'll upload the new .log file.

For what it's worth, I wasn't able to try the non-Ubuntu crash fix listed on the front page, because when I click on the link I get the "you do not have permission to access this page. This could be due to one of several reasons" dialog. Is there somewhere else that can be found at?

[sal_vager]

It may be defunct, I'll look into it but may have to remove it, though the segfault fix may be what you need and that is a few lines in the terminal.

It's really odd that there's no logs at all, which suggests a permissions issue, and yeah that KSP.log would be there because you ran KSP from your home folder

That it fails at Mono may mean Mono is not working, though KSP/Unity comes with its own modified Mono version, if you start KSP with ldd KSP.x86 | grep "not found" and ldd KSP.x86_64 | grep "not found" it'll show if any libraries are missing, though usually KSP wont start at all without a library.

[WolfgangAxel]

I reran ldd with both executables and nothing came up as not found, so nothing the game needs has been removed. Also, I'm not sure if it's failing at Mono because it does go on to list the button mapping of my xbox controller when it's plugged in. Unless of course Mono is what's creating that dialog.

Your comment on permission issues made me wonder about trying to run the game through sudo, which I know is a big no-no for a plethora of reasons. But, in the name of science I did it and interestingly enough it doesn't print the "aborted" text when it fails:

keaton@MissionControl:~/Documents/Kerbal Space Program$ sudo ./KSP.x86
[sudo] password for keaton: 
Set current directory to /home/keaton/Documents/Kerbal Space Program
Found path: /home/keaton/Documents/Kerbal Space Program/KSP.x86
Mono path[0] = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono/etc'
keaton@MissionControl:~/Documents/Kerbal Space Program$ 

keaton@MissionControl:~/Documents/Kerbal Space Program$ ./KSP.x86
Set current directory to /home/keaton/Documents/Kerbal Space Program
Found path: /home/keaton/Documents/Kerbal Space Program/KSP.x86
Mono path[0] = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Managed'
Mono path[1] = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono'
Mono config path = '/home/keaton/Documents/Kerbal Space Program/KSP_Data/Mono/etc'
Aborted
keaton@MissionControl:~/Documents/Kerbal Space Program$

The game still crashes and still doesn't generate a .log file, but it's interesting to me at least.

I've got a biochemistry test in 2 hours that I should probably prepare for, so I'll muck around with the kernel and any other suggestions after that tonight.

[sal_vager]

Luckily it's safe to run KSP with sudo, not recommended but not harmful, shame it didn't work though.

You missed a post by kemde though, he noticed you don't have a lot of RAM.

Hi,

WolfgangAxel. your log says RAM: 2615. With all those mods that might a bit short. Does KSP start unmodded ?

Or am i just reading something stupidly wrong ?

k

Though KSP should run in that if there's not other large applications running such as a browser, all the mods would have gone over that.

I really don't know what to try at this point.

[WolfgangAxel]

I definitely didn't see that post. Right now, it's starting completely unmodded- straight from the steam directory that's never been executed. I know I don't have a ton of RAM, but I know what I put on there should have been fine because: 1) I prune everything that I could use a procedural part for, so no tanks, wings, or fairings in any part mods, and 2) I run basically the same modlist on my Windows half of the computer with no memory issues, and that usually has Steam and anti-virus and god knows what else running at the same time. I'm usually very conscious of my memory usage, and for what it's worth, I've only ever hit my memory limit once in my KSP career. Furthermore, I don't think memory issues apply when the game doesn't get past mono loading.

The 3.16.0 image is downloading currently, so after a quick reboot I may or may not have another .log file to look at.

--Edit--

Booted into 3.16.0, ran KSP.x86 and got the same abort on startup. I'm at a loss as to what made it stop loading if that wasn't it. I'll scroll through my terminal history and see if I can find any other possible culprits, but I'm still not hopeful.

--Edit 2--

I had been starting the game through the OpenBox menu, so I don't have history of how many times I tried to launch the game, however I can see in my .bash_history that the first terminal work I did to try to fix the game was update the kernel to 4.2.0. It looks like I ran apt-get dist-upgrade right before rebooting into the new kernel, so it's probable that something that command updated completely broke something necessary for KSP (as opposed to whatever somewhat broke KSP in the first place). So unless there's an update history or somewhere where I can find the output of that command, there's no way to tell what the issue is.

I really hope that segfault error is the issue, and that the solution can be unlocked for all to see again.

Edited September 15, 2015 by WolfgangAxel

[sal_vager]

Okay, if it's any help I'm able to run KSP fine on 3.19.0-28-generic.