Re: libzip5 missing from hirsute?
On 4/10/21 7:55 PM, chris hermansen wrote: Hello fello quality team members, Testing hirsute on my new computer and whilst installing QGIS I note that libzip5, which is in focal and groovy, is missing from hirsute, which only seems to have libzip4. Any thoughts on where to report this beyond tossing it into the discussion here? Greetings, https://packages.ubuntu.com/groovy/libzip5 Looks like the maintainers are ubuntu-devel-disc...@lists.ubuntu.com . Maybe ask there and see if someone can give you more details on why it hasn't been built yet. You might want to look through the archives to see if anyone has mentioned it though: http://lists.ubuntu.com/archives/ubuntu-devel-discuss/ Hope that helps. Ed -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: NVidia RTX 3060 and 21.04
On 4/10/21 10:38 PM, chris hermansen wrote: > Hello again everyone, > > Hoping to beg a bit of advice. I have a brand new computer with an NVidida > RTX 3060 and I'm running the daily 21.04 on it. Install goes fine but > "after awhile" I seem to end up with a manually installed driver for the > RTX and "after a bit more while" all of a sudden I'm looking at a 1320 X > 768 display. > > I've made this problem go away temporarily with > > sudo apt purge nvidia-\* > > and poof I'm back to a reasonable 1920 x 1080 display. > > As far as I know I did not "manually install" anything. I'm a bit lost as > to how to report this as a bug, given that it's an NVidia thing and also > this weird "manually installed" package. > > If anyone has any suggestions I'd be most grateful. > Greetings, It's been a long time since I've used Nvidia on Ubuntu. So I'm going to start with a package I know. Hopefully I don't simplify my explanation to the point of being incorrect. :-D Linux-generic is a "package" that really isn't a package. It's more like a pointer to the latest version of the kernel. If you never flush out old kernels when you update, eventually (I think it's three old versions??) you will find that the repo no longer lists the kernels as available and apt will then basically say "I can't find this package anymore in the source list so therefore this package must have been installed manually." And that's how you can end up with "manually" installed packages that were actually installed by Ubuntu - it happens all the time. My *guess* is that you have an nvidia pointer package that is installing drivers for you. Eventually the version you are running is falling out of sync with the upstream source and thus your specific version is falling into "I can't find it anymore so it must be a manual install". Also, *IF* I remember correctly NVidia drivers are built to a specific version of the kernel but can be "loosely" linked. Thus, an NVidia driver for kernel 5.4.0.66.68 could work on 5.4.0.66.69 without recompile provided that nothing major changed in the kernel specific to its hooks. But eventually, you will update to a version of the kernel that isn't loosely linked and if the nvidia driver isn't automatically rebuilt with the update then things are going to go very poorly in driver quality. Here's my suspicion. If removing the NVidia drivers solves your problem, then you are wanting to stay on the nouveau drivers. Some update some where is telling your system to update to the NVidia drivers. They get out of sync and those drivers are then listed as "manual". Eventually those drivers clash/conflict with the latest kernel update and you end up with a bad display. I most often see this kind of thing happen with auto-updates in the background that pick the "best" option for you. [quick side rant] Telling someone to disable auto-updates is **TERRIBLE** advise. But this non-sense about drivers getting out of line is _precisely_ why I disable auto-update. I _loath_ it when I leave a perfectly functional system one night and log in the next morning to a busted upgrade... But I'm also paranoid and responsible enough that I subscribe to all the RSS feeds for all the security notices on my systems and I have planned times when I apply updates... But because the vast majority of users can't be bothered to actually do regular updates, then updates have to be forced on them automatically to prevent massive security issues and evil botnets which unfortunately means user systems "break unexpectedly". *sigh* [end rant] So what should you do? If you really don't want the NVidia drivers, then open up "software sources" and look for the "additional drivers" tab. Make sure that NVidia is disabled here. If you *DO* want the NVidia drivers, then make sure the appropriate driver is selected (if I recall correctly, there's like a stable, beta, and maybe something else?). And if you can't find "software sources", drop to the command line and try typing `software-properties` then hit the tab key to see if there are auto-completes for qt or gtk or whatever. It *should* be installed already if you did a default Ubuntu install though. From that same interface, on a different tab, you can also check to see what updates happen, and at what time interval updates are checked for and applied. I recommend you at least knowing what frequency this might be occurring on your system. Also, Ubuntu can churn through kernels. I recommend staying on top of any automated process that is updating behind the scenes. Knowing when and how often your computer is updating the kernel and then verifying if it is installing the nvidia drivers along side it might help you narrow down the who. Once you find the who - then you can file a bug report. It's been too long since I've really poked at the auto-update process for Ubuntu (besides just flat out turning it off!). I honestly don't remember t
Issue with one of the torrent files for 20.04
Greetings, I've been seeding the torrent files all morning for 20.04. Been pushing a full pipe all day! Congrats to all who helped make it a reality! :-D There's one torrent that seems to have issues. I'm still seeding to quite a few people, but I get "Tracker gave an error: Requested download is not authorized for use with this tracker". I thought maybe I'd just pulled it too soon or something, so I just now pulled the torrent. The file checked out and started seeding again. But I am still getting the error. http://cdimage.ubuntu.com/ubuntu/releases/20.04/release/ubuntu-20.04-live-server-arm64.iso.torrent Anyone else able to replicate? I don't see any other seeds, but it might be because the announce is bad. I'm certainly uploading is so I know others are out there using it. And none of the other torrents are acting up so I'm not sure what is going on with this one. Thanks! ~S~ -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Lubuntu 20.04 testing feedback
Greetings, I thought I'd pass along a bit of feed back. I will start with the easy one. I tested the 20200413 daily live focal-desktop-amd64.iso on the MS Surface Pro2. Not only could I _not_ find a problem with it, I was SO impressed by how much better and responsive it was vs 18.04 (the OS previously installed). The detachable keyboard was sometimes hit-and-miss on if it would work on 18.04, but no matter how or what I tried I couldn't get it to fail with the 20.04 beta. I'm really impressed! Thank you and congratulations to all involved. The more interesting one is an HP 14-dq1033ci. I initially started with this iso: lubuntu-20.04-beta-desktop-amd64.iso . I found two things wrong that were not an issue on 19.10 but I think both are driver related and I'm not sure where to report a bug for them. 1. There was SERIOUS video tearing whenever there was any kind of movement on the screen. However, after today's intel-media-va-driver update to 19.4.0r+dsfg1-1 (at least, I'm guessing at this because it was the only thing that even semi-related package that makes sense), the vast majority of the tearing went away. If I click and hold the title of a window and move it around really fast, I can see it a little bit. And there are a few icons when I hover over them there will be a line through the icon until the next refresh, but there was SIGNIFICANT improvement after today's update. I did check, and I have all the relevant Intel driver packages (that I know about anyway) so I don't think I'm missing anything. I just never saw this kind of screen tear with this laptop using 19.10. 2. The web cam no longer works at all. If I start any program (such as Cheese), it is just a black screen. Shortly after boot this error below is in dmesg. To be honest, I've not had time to really research the issue so it could be something trivial on my end, but I thought I'd report it tonight since I've done a lot of testing yesterday and today. :-) [3.176709] uvcvideo 1-3:1.0: Entity type for entity Extension 4 was not initialized! [3.176712] uvcvideo 1-3:1.0: Entity type for entity Extension 3 was not initialized! [3.176714] uvcvideo 1-3:1.0: Entity type for entity Processing 2 was not initialized! [3.176716] uvcvideo 1-3:1.0: Entity type for entity Camera 1 was not initialized! [3.176807] input: HP TrueVision HD Camera: HP Tru as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input13 Overall, I'm SUPER impressed and VERY appreciative of all the hard work that people have put into this release. It looks like it is easily the best release yet! (and since I tend to jump LTS to LTS, I've even more excited about how great this beta has been in my testing!) Thank you all! ~S~ -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Help Needed Testing Lubuntu 18.10 Cosmic Cuttlefish Beta!
On 10/02/2018 09:31 PM, EdLesMann wrote: > > On 10/02/2018 06:47 PM, Walter Lapchynski wrote: >> On 2018-10-02 16:38, EdLesMann wrote: >>> The only "oddity" is this. Why is there an option to install Lubuntu on >>> my desktop after I've installed Lubuntu? ;-) >> >> That is strange, and not something I can reproduce. We actually >> [explicitly remove the installer][1]. Maybe you didn't restart? Or you >> didn't remove the installation media before restarting? >> >> [1]: >> https://phab.lubuntu.me/source/calamares-settings-ubuntu/browse/master/lubuntu/modules/packages.conf$5 >> > > Greetings, > > I did remove the USB and was booted into the new install. I did explore > it a bit, the calamares application and most of the stuff was gone but > the desktop icon was still there. Is it possible it was copied when the > home directory was setup/configured? (just a crazy thought of mine) > > I just spent an hour poking at the new install and setting up my > workflow. Not sure I want to blow the install away. However, I can > install it into a VM later and see if I can reproduce. > Greetings, I am 0 for 2 in the VM's - looks like it gets removed. However, I'm 2 for 2 when reinstalling on my physical laptop. I did a bit more digging around and it looks like it is all gone but the Desktop icon/script. As it takes a while on my laptop, I won't try a third time tonight. I used this ISO for my testing: http://cdimage.ubuntu.com/lubuntu/daily-live/20181002/cosmic-desktop-amd64.iso I used the usb-creator-gtk tool on a 18.04 laptop to make a USB install. I used the same USB for all of the installs. Not sure if that helps or not. Thanks! -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Help Needed Testing Lubuntu 18.10 Cosmic Cuttlefish Beta!
On 10/02/2018 06:47 PM, Walter Lapchynski wrote: > On 2018-10-02 16:38, EdLesMann wrote: >> The only "oddity" is this. Why is there an option to install Lubuntu on >> my desktop after I've installed Lubuntu? ;-) > > That is strange, and not something I can reproduce. We actually > [explicitly remove the installer][1]. Maybe you didn't restart? Or you > didn't remove the installation media before restarting? > > [1]: > https://phab.lubuntu.me/source/calamares-settings-ubuntu/browse/master/lubuntu/modules/packages.conf$5 > Greetings, I did remove the USB and was booted into the new install. I did explore it a bit, the calamares application and most of the stuff was gone but the desktop icon was still there. Is it possible it was copied when the home directory was setup/configured? (just a crazy thought of mine) I just spent an hour poking at the new install and setting up my workflow. Not sure I want to blow the install away. However, I can install it into a VM later and see if I can reproduce. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Help Needed Testing Lubuntu 18.10 Cosmic Cuttlefish Beta!
Greetings, It wasn't until tonight that I had the opportunity to install on my laptop. Everything has gone really smoothly so far. Whoo! The only "oddity" is this. Why is there an option to install Lubuntu on my desktop after I've installed Lubuntu? ;-) I poked around in the bug tracker but didn't see anything about it. I will report any other bugs with the ubuntu-bug tool. Thanks! On 09/26/2018 06:46 PM, monetaryabyss wrote: > This will be the first Beta of Lubuntu with LXQt! The Lubuntu team > development team has been working hard on getting the 18.10 Cosmic Cuttlefish > Beta ready and needs your help! > With the switch from the LXDE desktop environment to the LXQt desktop > environment there is a great amount of testing still needed. We need you to > explore and report any bugs that you find. > The release schedule for Cosmic Cuttlefish can be found here: > https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseSchedule > The Lubuntu wiki page for testing can be found here: > https://phab.lubuntu.me/w/testing/ > > Thank you on behalf of the Lubuntu QA Team. > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Showstopper bug report (17.04): WiFi not working
On 05/04/2017 11:24 AM, Magnus Määttä wrote: > Hi, > > I guess this is the address to send mail to for bug reports since there > aren't any valid working other ways to do it. > The website doesn't have any working link to any bug-report form and the > "ubuntu-bug" utility thinks I want to report a bug with the resolution > or graphics when selecting "other problem" and > is trying to include information from this other system which is > actually working (version: 16.10). > > Anyway. Since installing Ubuntu/Kubuntu 17.04, WiFi network connectivity > doesn't work anymore. It works just fine with all other equipment known > to man except any equipment updated to version 17.04, which seems to be > a real showstopper for 17.04, so ideally it (17.04) should be recalled. When you file a proper bug report, please post back. I just did an upgrade from 16.10 to 17.04 on my surface pro 2 tablet and wifi straight up dies. Tells me that the password isn't correct in the log files (it is). So I did a fresh install of 17.04, same thing. Just did a fresh install of 16.10 and wifi works again. I've just been busy this afternoon and haven't filed a report, so if yours is anything like mine I will add a "me too!" with the information I have. Ed -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Hi!
On 07/30/2016 05:19 AM, Ian Bruntlett wrote: [snip] > I have produced an illustrated brief guide to Lubuntu Linux that is handed > over to people when they are given a lubuntu PC. It can be downloaded from > the bottom of this page - > https://sites.google.com/site/ianbruntlett/home/free-software and you are > welcome to give it to your users. Dude, nice! I like that. I have bookmarked that site for the next time I hand someone a Lubuntu install. Thanks!! -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Upgrade from 14.04 to 16.04 went bad
On 03/29/2016 12:50 PM, Alberto Salvia Novella wrote: > EdLesMann: >> Most of the guides I see online for submitting bug reports >> kinda require the system to be in a mostly working state. > > You can do this!: > (https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_at_Launchpad.net) Thanks! I did some digging around and chris hermansen also helped by sending me a few links. It seems that a lot of the error messages that turned up in my log are reported already. I added a 'me too' to a few of them. I am planning on rebuilding the laptop from scratch later. I guess my 14.04 systems will just have to stay 14.04 for a while until I can rebuild them to 16.04. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Upgrade from 14.04 to 16.04 went bad
Greetings,
Every system I have is Lubuntu. Just getting that out there at the
beginning. :-)
I have been tinkering with and using the 16.04 daily builds for a while
on a few I-really-don't-care-what-happens-dev-boxes. Things have been
pretty solid so far. The few bugs I found I reported, but no major
issues. I have many 14.04 systems that I am planning on updating to
16.04. I thought I would test a few of the systems I don't care so much
for and see how an update goes.
The first was a VM. It threw a bunch of weird messages about systemd and
init packages, but completed and seems to be functioning...but it isn't
really anything more then a default install (I roll back my test changes
to a base install + updates).
I decided to test something a bit more real (but expecting it to have
issues). The laptop I occasionally play steam games on but mostly just
watch movies in bed with.
Oh no...it did not go so well.
First, A LOT of messages about systemd and init packages conflicting or
missing.
Second, I got an error saying that there were too many errors. That was
slightly terrifying and my first sinking feeling that this wasn't going
to end well...But it sent me on to a dpkg recovery process so that made
me feel a bit better until...
Third, I got errors about the dpkg repair process (something about not
being able to write apport errors because they already existed)...uh oh;
no more warm fuzzies for me...
Fourth, at this point I have just been clicking 'OK' letting the
installer do its thing through all of these error messages and as it was
doing something about those dpkg repair messages, it got to the point
where it was rebuilding the DKMS kernel modules...then the screen went
blank...but I could still tell the laptop was doing /something/. At the
very least the caps light still turned on and off but I couldn't see any
other sign of life. After about 30 minutes of just sitting there, I
checked again and it was just dead. No light changes with caps/num lock,
no virtual terminal switching, nothing at all. I couldn't even ssh into
the laptop any more. So I hard rebooted. Insta-kernel-panic. As soon as
I start to boot, it just dies. None of the kernels (pre or post update)
work. I tried a few tricks and it just flat out panics.
The good thing is that there really isn't anything on this laptop I care
about. I can easily wipe and start over. I can also liveCD boot and
check out the disk contents too.
However, before I do a re-install to 16.04 I thought it was worth asking
if there is interest in me attempting to salvage logs or do any kind of
post-mortum. Most of the guides I see online for submitting bug reports
kinda require the system to be in a mostly working state. This one
ain't. Not even close. A liveCD is the best I can do for this guy right now.
What logs should I get? How much should I provide?
I really want smooth updates for my other 14.04 boxes which is why I
wanted to test and give feedback now. I expected issues, but I didn't
quite expect a complete insta-panic. :-{
Anyway, if there is anyone interested in trying to figure out what went
wrong, let me know. I will gladly pull whatever information you want.
Anything I can do to help make this smoother later on. :-)
Thanks!
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Having issues getting hardinfo to work on Xenial
Greetings, I skipped the hardinfo as it isn't needed and I did a lot of the testing procedures. Everything worked as expected except for middle clicking (reported that already). Well, I just discovered another issue. Starting out in the dock, everything works as it should. Unplug from the dock and everything continues to work. Plug back into the dock, and complete freeze with a black screen. Hard reset required. On reboot I didn't see anything in particular that looked interesting in the logs for why the crash. What information should I provide and to whom? Thanks! -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Having issues getting hardinfo to work on Xenial
On 01/23/2016 12:19 PM, Nio Wiklund wrote: [snip] > > Maybe you can discuss it in the following thread at the Ubuntu Forums :-) > > Surface Pro 3 - USB/MicroSD Only Install > > http://ubuntuforums.org/showthread.php?t=2309963 Thanks for the link. I did search around before posting about what others are doing. I didn't see anything in particular about hardinfo not running though. I did find a post saying that for hardinfo to run correctly, it needed multilib support. That is a bit boggling to me. When I run hardinfo against file it clearly states it is 64bit ELF. But since I don't really care about this install, I installed lib32z1. That still didn't work either. I think that poster was confused or I don't understand something. There also seems to be a bit more discussion about Pro3 then 2 out there. Don't know why. Then again, I have only mucked about with the Surface for less than a day so far and everything I know about the Surface is from this experience. :-) I will have to give this back (probably next week...the windows admin will have to reimage it and will probably be a bit pissed at me :-), but from my short time with it running Lubuntu I actually kind of like the hardware. I may have to see about picking up a refurb for cheap. Thanks! -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Having issues getting hardinfo to work on Xenial
Greetings, I had a Surface Pro 2 dumped on my desk at work. WTH am I going to do with this? Hrm...Will Ubuntu install? I had a 13.04 Lubuntu disk sitting near by...and it installed! But i didn't like the upgrade. Never really booted after that. If I am going to test, might was well do a proper test using the latest version. I grabbed a copy of Lubuntu Xenial 16.04 Daily Build From 2016-01-22. Smooth install. Smooth update. I have tested a bunch of my normal stuff and things are working great. Maybe I should tell someone! Maybe I should to testing based on the Ubuntu Laptop testing guide. That way I do a proper test and not just the few apps I use. Besides, why not? :-) The system is fully updated. Following this: https://wiki.ubuntu.com/Testing/Laptop/Procedures It says to get my hardware from this: https://wiki.ubuntu.com/QATeam/Hardware Which asks me to run this: hardinfo -ram devices.so | sed '/\*\*\*\*\*\*\*/,/\*\*\*\*\*\*\*/d' | gist-paste However, $ hardinfo -ram devices.so Computer Summary sh: 1: /lib/libc.so.6: not found Segmentation fault (core dumped) OK fine.. $ sudo ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib/libc.so.6 $ hardinfo -ram devices.so Computer Summary Segmentation fault (core dumped) Well that popped up a "would you like to submit this crash to Ubuntu" window. Yes. But then it went away...not sure if it actually did submit. Hrm. If I try to have hardinfo generate a report, it fails and outputs a 0 byte file. Having never generated a testing report for Ubuntu before I am hesitant to continue the testing process when I can't seem to get past step 1. :-( Thoughts? $ lsusb Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0424:5537 Standard Microsystems Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 045e:0795 Microsoft Corp. Bus 001 Device 008: ID 045e:0794 Microsoft Corp. Bus 001 Device 007: ID 03eb:8209 Atmel Corp. Bus 001 Device 005: ID 045e:07a9 Microsoft Corp. Bus 001 Device 010: ID 1286:2044 Marvell Semiconductor, Inc. Bus 001 Device 011: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 006: ID 0572:143e Conexant Systems (Rockwell), Inc. Bus 001 Device 004: ID 045e:07ab Microsoft Corp. Bus 001 Device 002: ID 0424:2137 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz stepping: 1 microcode : 0x17 cpu MHz : 1835.937 cache size : 3072 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm xsaveopt bugs: bogomips: 4988.44 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz stepping: 1 microcode : 0x17 cpu MHz : 1812.402 cache size : 3072 KB physical id : 0 siblings: 4 core id : 1 cpu cores : 2 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx
