Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I type in 1spci, sudo 1spci, 1smod or sudo 1smod it says that they are bad commands or they aren't found or something like that. What do I do next?
Hi...
This is because you're using the number "1" instead of the letter "l" or "L". Try doing it again using the "l," as in lspci.
Using the l or "L" instead of 1 works, but there is so much info. What exactly should I be looking for? And how does one scroll through the pages of info that zips by so fast?
Using the l or "L" instead of 1 works, but there is so much info. What exactly should I be looking for? And how does one scroll through the pages of info that zips by so fast?
Hi...
There shouldn't be that much info from lspci but if you would, please copy and paste the entire output from the command I gave you into your next post. Most, if not all, terminals I've seen in Ubuntu allow you to scroll up or down to see the entire output given from a command.
To be honest, I've never seen an lspci report look like that before. It looks garbled and I'm not sure what to suggest. Hopefully, someone who knows more will...
Distribution: Mainly Devuan, antiX, & Void, with Tiny Core, Fatdog, & BSD thrown in.
Posts: 5,511
Rep:
Quote:
Originally Posted by fwh4728
I reinstalled ubuntu 15.04. It took a lot longer to finish this time. It still won't go beyond the splash screen just past the sign in screen, but I can now sign in to the terminal function. I don't really know what I am doing with it. When I type in sudo dmesg about 4 or 5 pages fly by in a little over a second. When I type in 1spci, sudo 1spci, 1smod or sudo 1smod it says that they are bad commands or they aren't found or something like that. What do I do next?
This sounds like you have a bad download.
(Did you check it, there should be an md5 checksum or similar on the website from where you downloaded it.)
Edit: To see what gets spat out when text rolls off your screen, pipe it through less, such as,
Googling hints that your system uses a Pentuim D chip from intel. Supposedly a 64 bit dual core. Basically not sure why you're having this much issue unless you have some hardware issues. My first thought would be a fresh power supply. And check the cooling, it could by dying on the install due to thermal issues. You might also try pulling all the ram chips except the bare minimal in case you have some bad ram chips. The blotchy screen makes me wonder if your monitor isn't going out, but it could just be the video card and driver.
If you have another machine, you might install the OS on it and swap the drive into that one to boot it. This should get you a little further if you are having thermal issues.
Gateway rerun desktop computers runs linux just fine and dandy in my experience. I dug this throwaway out of a dumpster.
Just a old inxi report on the specs of it. I run MX-14 on it presently though. With a newer kernel.
Does there seem to be anything out of the ordinary in this lspci report? I did the dmesg | less. The report was at least 12 screens long, but I was able to scroll through it. Should it be that long normally? It was in black and white. The dmesg report is in color, but I cannot scroll through it. What should I do next? I did download the 64 bit iso and tried to load it, but it did not install at all. The ram passed all of the memory tests I ran on it. One of my boot cd's has a mini xp program on it. It runs fine on this computer, but I can't run ubuntu from the iso disks at all. The monitor works fine with other computers.
It shouldn't be missing things, but it might. If /proc/cpuinfo has " lm " in the FLAGS part then it is 64 bit. Otherwise it's NOT 64 bit, aka 32 bit. If /proc/cpuinfo has " pae " in the FLAGS then you don't need to do too much special. But if it doesn't have pae, Then that's something that will need special attention.
Shift + PageUP and Shift + PageDown will let you scroll in a terminal window.
Does there seem to be anything out of the ordinary in this lspci report?
Not that I can see. I run 32 bit isos on my emachine and not Ubuntu either.
If i had more ram in mine. I'd run a pae kernel. In a 32 bit iso install on that Emachine of mine.
Try and learn to use the code tag # symbol on advanced reply tool bar like I show below as a example of posting lscpi and dmesg readouts. I use the <snip> for leaving out cruft on a dmesg readout just for this example. Usually any errors is what you wish to keep in a dmesg post.
Code:
~$ cd /var/log
harry@misohorny1:/var/log$ ls
alternatives.log dmesg.1.gz lastlog samba
apt dmesg.2.gz lightdm syslog
auth.log dmesg.3.gz lite-software.log udev
boot dmesg.4.gz llupdates.log unattended-upgrades
boot.log dpkg.log lpr.log upstart
bootstrap.log faillog mail.err user.log
ConsoleKit fontconfig.log mail.info wicd
cups fsck mail.log wtmp
daemon.log gpu-manager.log mail.warn Xorg.0.log
debug hp messages Xorg.0.log.old
dmesg installer ntpstats
dmesg.0 kern.log pm-powersave.log
harry@misohorny1:/var/log$ cat dmseg
cat: dmseg: No such file or directory
harry@misohorny1:/var/log$ cat dmesg
<snip>
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
<snip>
[ 20.758434] ieee80211 phy0: hwaddr <filtered>, RTL8187BvE V0 + rtl8225z2, rfkill mask 2
[ 20.779868] rtl8187: Customer ID is 0x00
[ 20.783772] rtl8187: wireless switch is on
[ 20.783816] usbcore: registered new interface driver rtl8187
[ 21.686099] init: smbd main process (723) killed by HUP signal
[ 21.686113] init: smbd main process ended, respawning
[ 22.828039] floppy0: no floppy controllers found
harry@misohorny1:/var/log$
Putting a long readout in code tags compresses readout in a box with a scrollable side bar and makes the readout easy to read for forum members.
You might want to address the md5sum questions asked earlier also in your next post. Like did you do it?
I thought that also at one time shadow7. But my Emachine only boots 32 bit isos even though my inxi report posted earlier shows lm, pae and sse2 on that Pentium 4 D cpu.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
