lmao. That’s probably the issue I have though, which sucks. a buddy sent me this 24" monitor for free (he was just going to junk it or sell it or whatever), and I gave family the original LED monitor I used for so long LED 19" LG Flatron, which didn’t seem to give me much issues at all before. I think I got that one around same time I got the computer parts to build this tower. Of course resolution was like 1366 x 768 something.
I don’t know, but I like opensuse, and I like the KDE or whatever style operating systems, not the GNOME, and not sure if I need find distro that might be easier to work with and install drivers for or not. I can’t waste time trying to “jinny rig” things to get it working and then still borked else where (boot prompt screens, etc) lol. It’s weird, because I tried Linux Mint distro before, and ran a little script at start up and appeared to work for while. Didn’t have to mess with xorg.conf files etc. http://forums.linuxmint.com/viewtopic.php?f=213&t=130595
I’m not sure about Kubuntu, or just use and try regular Ubuntu, or go with Linux Mint or KDE Linux Mint (Cinnamon) etc… Wish more guys familiar with the resolution stuff would chime in here, it’s like I’m almost there to finish line, but not quite… lmao. I can’t really afford graphic cards either, which sucks. Or, just take back my old monitor and use that, but I’ll miss this big 24" monitor Lol.
I’m not sure about Kubuntu, or just use and try regular Ubuntu, or go with Linux Mint or KDE Linux Mint (Cinnamon) etc… Wish more guys familiar with the resolution stuff would chime in here, it’s like I’m almost there to finish line, but not quite… lmao. I can’t really afford graphic cards either, which sucks. Or, just take back my old monitor and use that, but I’ll miss this big 24" monitor Lol.
Well, gogalthorp has essentially covered the ground already.
From the grub2 boot screen, you can press ‘c’ to drop to console mode. From there, entering ‘vbeinfo’ will give you a list of framebuffer display modes that your graphics card advertises as supported. Press [ESC] key to leave console mode, and continue booting. Sometimes, the wrong mode is used, so this can be changed by editing /etc/default/grub changing the ‘GRUB_GFXMODE’ parameter
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
ah okay, i was wondering how to enter the grub thing, but it blinks by so fast, don’t give me much time to do anything with it Lol. barely even notice it’s there during boot. i posted the vbeinfo in an earlier post, ran command from terminal or whatever? Or maybe it was little different commands, here below…
yeah, i tried 1920x1200x24, or 1920x1200x60 or some such for GFX_MODE, didn’t do nothing. Even though it was claiming I could do 1920x1440, which should be bigger than 1920x1200 right? So I was a little smaller than it’s claiming I could do… ? Lol. I’m going to have to really figure out WHAT specs my monitor has, HOW to set it up correctly etc. I wish there was an online xorg automatic creation tool to use, it some how reads my monitor / computer specs, and creates the files itself and spits them out for me download them and use them lmao.
Another thing I forgot to add previously, the monitor that was given to me had some minor water damage, the little circuit board where the VGA cord connects too had some lightish green/blue-ish corroded build up on it and i cleaned it up with some rubbing alcohol to make it nice and clean. Wasn’t much build up of gunk though, but maybe the VGA cable had some in it’s pins or whatever… Maybe the pins in the back where it plugins into monitor isn’t great either, I’m not sure.
Because when I fire up tower, it sometimes goes through the various modes before registering it’s D-SUB, sometimes says PC-MODE, and couple others. Other times it’s giving like “Input Not Supported”, but I think that’s when I was doing the grub edits for various sizes or xorg.conf edits… It’s weird, because it’s like the monitor isn’t being registered with the operating system.
I went and removed OpenSuse, installed Kubuntu 15.04 or whatever once, because those intel-linux-drivers for ubuntu / fedora etc supported 15.04 Kubuntu … to see how those worked. And it’s not even registered with xorg at all. No 50-monitor.conf file, no 50-device.conf file, no 50-screen.conf file at all. In system settings > display / monitor … it’s not listing the resolutions after Kubuntu was installed, just gives button to “unify outputs”, then apply so resolutions are visible. Well I did that, applied it, rebooted, and it was back again where no resolutions are displayed, with “unify outputs” button there again. Like the changes I’ve done, to display resolutions didn’t work. Like “break unified outputs” option is sticking “on”.
I did another thing too, I installed EDID “test” thing. Out put of that is below here, not sure how to read it? Lol…
sudo get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
Looks like no busses have an EDID. Sorry!
Attempting to use the classical VBE interface
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0x11100 "Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS"
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again
Something isn’t right some where, maybe the monitor is on last leg? Maybe the VGA port is ****, the cable is ****, or too “new” for the chipset / motherboard of mine… or maybe the conf files aren’t setup just right, hard to say. I’m not liking Kubuntu 15.04 though, probably will come back to OpenSuse Tumbleweed … Hopefully then get this setup right with all guy’s help.
Looks like it failed. Either the chip or the monitor support EDID or maybe cable or connector etc. But in any case the chip and the monitor are not talking and thus the chip does not know the monitors capabilities. So things are dicey until the xorg kicks in and forces things.
yeah, that makes sense though. because it did work before, had a nice 1920x1200 resolution and was detected by the OS. Some where in my swapping towers (I have two of them, one with windows 7, one with Linux Mint on.), I disconnect the monitor cable at tower of course to easily swap towers out, I might not have tightened up those locking screws on end of cable at tower, so it didn’t have solid tight connection.
I just went downstairs now to get cable off that littler LED 19" to see if maybe it’s the cable itself, and put it on main tower (I run linux on), tightened up the screws, and fired up 24" tower with USB / OpenSuse Tumbleweed install ISO on it, and it appears to be displaying right / properly now.
I’m running the installer now, and it appears nice and big resolution. Perhaps since I didn’t have those cable locking screws tightly screwed down, it wasn’t keep good solid connection. Some times I just plug cable in hand tight without tightening those screws in just in case I have to swap towers again lol.
I guess only way to find out though, is to wait for installation to be done, and use computer a while and see what happens. If the resolution is lost during use, then it’s more than the cable / tightened cable to tower. I’ll then have to get my little monitor back from family and use it, and let them use their friend’s monitor. Thanks for your help guys.
Quick update (tried to edit previous post but it wouldn’t let me, don’t like to bump threads much), under Settings > Display / Monitor, it shows 1920x1200 and lists my monitors model/make (VGA LCD24WMCX). So hopefully this sticks and continues working lol. However, I did get a plasma crash prompt / popup after getting to desktop. I’m not sure if it’s because I pulled out the USB stick too early (which contained install ISO for tumbleweed), maybe should have left that in until I got to desktop? I reported it via the popup about the crash.
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f04bb8d4880 (LWP 3394))]
Thread 8 (Thread 0x7f04a4f3c700 (LWP 3396)):
#0 0x00007f04b4f0832d in poll () from /lib64/libc.so.6
#1 0x00007f04b9d30332 in ?? () from /usr/lib64/libxcb.so.1
#2 0x00007f04b9d31e17 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3 0x00007f04a728c7f9 in ?? () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4 0x00007f04b55f3eaf in ?? () from /usr/lib64/libQt5Core.so.5
#5 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#6 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 7 (Thread 0x7f049e6f9700 (LWP 3440)):
#0 0x00007f04b1660b54 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1 0x00007f04b161c909 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f04b161ce38 in ?? () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f04b161cf9c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#4 0x00007f04b581820b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f04b57c15ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6 0x00007f04b55ef13c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7 0x00007f04b8814ce5 in ?? () from /usr/lib64/libQt5Qml.so.5
#8 0x00007f04b55f3eaf in ?? () from /usr/lib64/libQt5Core.so.5
#9 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 6 (Thread 0x7f0491671700 (LWP 3445)):
#0 0x00007f04b4f0832d in poll () from /lib64/libc.so.6
#1 0x00007f04b161ce94 in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f04b161cf9c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f04b581820b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007f04b57c15ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f04b55ef13c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f04b8814ce5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7 0x00007f04b55f3eaf in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#9 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 5 (Thread 0x7f048b5f7700 (LWP 3449)):
#0 0x00007f04b471607f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1 0x00007f04bafa17f4 in ?? () from /usr/lib64/libQt5Script.so.5
#2 0x00007f04bafa1839 in ?? () from /usr/lib64/libQt5Script.so.5
#3 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#4 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 4 (Thread 0x7f048a622700 (LWP 3450)):
#0 0x00007f04b4f0832d in poll () from /lib64/libc.so.6
#1 0x00007f04b161ce94 in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f04b161cf9c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f04b581820b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007f04b57c15ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f04b55ef13c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f04b8814ce5 in ?? () from /usr/lib64/libQt5Qml.so.5
#7 0x00007f04b55f3eaf in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#9 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 3 (Thread 0x7f04022a5700 (LWP 3451)):
#0 0x00007f04b4f0832d in poll () from /lib64/libc.so.6
#1 0x00007f04b161ce94 in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f04b161cf9c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f04b581820b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007f04b57c15ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f04b55ef13c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f04b938dae2 in ?? () from /usr/lib64/libQt5Quick.so.5
#7 0x00007f04b55f3eaf in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#9 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x7f03ed1bb700 (LWP 3462)):
#0 0x00007f04b4f0832d in poll () from /lib64/libc.so.6
#1 0x00007f04b161ce94 in ?? () from /usr/lib64/libglib-2.0.so.0
#2 0x00007f04b161cf9c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3 0x00007f04b581820b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#4 0x00007f04b57c15ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#5 0x00007f04b55ef13c in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6 0x00007f03ef6c5b77 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so
#7 0x00007f04b55f3eaf in ?? () from /usr/lib64/libQt5Core.so.5
#8 0x00007f04b47104a4 in start_thread () from /lib64/libpthread.so.0
#9 0x00007f04b4f10cad in clone () from /lib64/libc.so.6
Thread 1 (Thread 0x7f04bb8d4880 (LWP 3394)):
[KCrash Handler]
#6 0x00007f04b870119d in QV4::MemoryManager::collectFromJSStack() const () from /usr/lib64/libQt5Qml.so.5
#7 0x00007f04b87012c3 in QV4::MemoryManager::mark() () from /usr/lib64/libQt5Qml.so.5
#8 0x00007f04b8701cb8 in QV4::MemoryManager::runGC() () from /usr/lib64/libQt5Qml.so.5
#9 0x00007f04b8702b43 in QV4::MemoryManager::allocData(unsigned long) () from /usr/lib64/libQt5Qml.so.5
#10 0x00007f04b872c75b in ?? () from /usr/lib64/libQt5Qml.so.5
#11 0x00007f04b872e81c in QV4::Object::Data::Data(QV4::InternalClass*) () from /usr/lib64/libQt5Qml.so.5
#12 0x00007f04b86f06a2 in QV4::ExecutionEngine::newArrayObject(int) () from /usr/lib64/libQt5Qml.so.5
#13 0x00007f04b881154d in ?? () from /usr/lib64/libQt5Qml.so.5
#14 0x00007f04b88109ee in ?? () from /usr/lib64/libQt5Qml.so.5
#15 0x00007f04b8810f84 in ?? () from /usr/lib64/libQt5Qml.so.5
#16 0x00007f04b88109ee in ?? () from /usr/lib64/libQt5Qml.so.5
#17 0x00007f04b8810f84 in ?? () from /usr/lib64/libQt5Qml.so.5
#18 0x00007f04b88109ee in ?? () from /usr/lib64/libQt5Qml.so.5
#19 0x00007f04b88128d2 in ?? () from /usr/lib64/libQt5Qml.so.5
#20 0x00007f04b8812c6b in ?? () from /usr/lib64/libQt5Qml.so.5
#21 0x00007f04b880f4cd in ?? () from /usr/lib64/libQt5Qml.so.5
#22 0x00007f04b880fe91 in ?? () from /usr/lib64/libQt5Qml.so.5
#23 0x00007f04b8810f84 in ?? () from /usr/lib64/libQt5Qml.so.5
#24 0x00007f04b88109ee in ?? () from /usr/lib64/libQt5Qml.so.5
#25 0x00007f04b8810f84 in ?? () from /usr/lib64/libQt5Qml.so.5
#26 0x00007f04b879ec07 in ?? () from /usr/lib64/libQt5Qml.so.5
#27 0x00007f04b879f45c in QQmlIncubationController::incubateFor(int) () from /usr/lib64/libQt5Qml.so.5
#28 0x00007f04b986d3fc in ?? () from /usr/lib64/libKF5Declarative.so.5
#29 0x00007f04b879f2c9 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /usr/lib64/libQt5Qml.so.5
#30 0x00007f04b879ad5c in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /usr/lib64/libQt5Qml.so.5
#31 0x00007f04b985da62 in KDeclarative::QmlObject::createObjectFromComponent(QQmlComponent*, QQmlContext*, QHash<QString, QVariant> const&) () from /usr/lib64/libKF5Declarative.so.5
#32 0x00007f04bb2c9bbd in ?? () from /usr/lib64/libKF5PlasmaQuick.so.5
#33 0x00007f04bb2ca166 in PlasmaQuick::AppletQuickItem::setExpanded(bool) () from /usr/lib64/libKF5PlasmaQuick.so.5
#34 0x00007f04bb2cd9a9 in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libKF5PlasmaQuick.so.5
#35 0x00007f048a638777 in ?? () from /usr/lib64/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so
#36 0x00007f04b879674f in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags<QQmlPropertyPrivate::WriteFlag>) () from /usr/lib64/libQt5Qml.so.5
#37 0x00007f04b876271b in QV4::QObjectWrapper::setProperty(QObject*, QV4::ExecutionContext*, QQmlPropertyData*, QV4::ValueRef) () from /usr/lib64/libQt5Qml.so.5
#38 0x00007f04b8762c76 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionContext*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::ValueRef) () from /usr/lib64/libQt5Qml.so.5
#39 0x00007f04b8762d9b in QV4::QObjectWrapper::put(QV4::Managed*, QV4::String*, QV4::ValueRef) () from /usr/lib64/libQt5Qml.so.5
#40 0x00007f04b876986d in QV4::Runtime::setProperty(QV4::ExecutionContext*, QV4::ValueRef, QV4::String*, QV4::ValueRef) () from /usr/lib64/libQt5Qml.so.5
#41 0x00007f048aa1229f in ?? ()
#42 0x000000000000fff7 in ?? ()
#43 0x00000000040418c0 in ?? ()
#44 0x0000000004aa5f90 in ?? ()
#45 0x000000000000000c in ?? ()
#46 0x000000000000000a in ?? ()
#47 0x00007f049776d67e in ?? () from /usr/lib64/dri/i915_dri.so
#48 0x0000000000000000 in ?? ()
Back on about the swapping towers out -when I do the swapping of towers, I think I might have originally installed the Linux Distro on this main tower, then unplugged it and hooked it up on other side of the desk here to smaller monitor (older model; Compaq FP5315) which has 1024x768 resolution in it. Then put the smaller tower (less ram, older motherboard (even older than this main tower’s is) on this monitor to do file sorting etc, while the main tower is on other monitor doing DBAN erasing of hard drive, etc. Maybe the swapping out of towers like that, goofed up the original registering of monitors and sizes. I do this swapping of monitors in order to be able to watch movies on this main work area cause I have the speakers etc here, so I can watch movies while the main tower got DBAN’ed.
In this case, last night, I ran DBAN (quick erase) on this main tower while I slept (didn’t swap towers at all this time), and “flashed/burnt” the OpenSuse tumbleweed ISO to USB stick on other smaller tower, and then did installation of OpenSuse just fine and it registered the monitor and displayed nicely during boot and installing it. It’s weird though, because I could have sworn at some point before, after installing a linux distro it was displaying fine, but only after doing updates via terminal and rebooting, it kicked it back to 1024x768. Not sure what happened there either lol. In any case, I hope it works now, and sticks lmao. I went and checked the 50-monitor.conf, 50-device.conf, 50-screen.conf files quick and it don’t have anything for monitor in them, so I guess it’s alright since it’s registered in Settings > Display / Monitor section?
I’m wondering, what graphic card would you suggest me to get for reasonable price? i’m limited to about 27.xx with free shipping included maybe on ebay. my brother could help me get one, but limited to like 27.00 to get it lol. oh, i talked to guy i got monitor from, he also had issues getting resolution to stick with linux OS’s, even with nvidia drivers.
he wrote
That is wild. I cannot remember the card but suspect it was a PCI video device I had issue with resolution stick for me in linux. But that was nvidia drivers and dkms not being on the proper kernel for the driver
i had gotten display right, disconnected vga cable… put another one on it… and it registered monitor in opensuse… but now its like black or dark grey SS bolts from nazi patches that sometimes flicker horizontally. if i mouse click the plain bar where browser tabs are at… it flickers/ jumps… till i stop mouse on it, if i right click on it, it jumps lmao. lately though too, when i reboot, i get error message at top of black screen about something not mounting right or whatever, when it boots up, i get ugly blue login prompt screen, not the nice orange styled one… weird.
Just updating people on here letting ya know what’s going on now. I ordered that GeForce 210 graphics card friday, got it yesterday, and hooked it up this morning earlier after doing dban on hard drive. Since it takes forever to download the full 4.7 gb DVD installer for opensuse, I used old DVD installer from 9/19/2015 …
I hooked up the single link DVI-D to HDMI cable. There’s dual DVI-D link port in back of monitor, and HDMI port in graphic card. It’s the only way I could hook it up I have no HDMI to HDMI cable. I used the old DVD installer burnt to USB stick and installed OpenSuse Tumbleweed…
During installation process, it registered monitor as DVI. I got through to desktop, checked settings for monitor, it listed all these various screen resolutions, and the monitor by model and such. It didn’t do this before with VGA cable. So since I used old DVD installer I then ran Zypper Update, figured I’d let it run while I slept. I woke up to see error at grub loading…
error: file ‘/grub2/i386-pc/normal.mod’ not found.
entering rescue mode…
So not sure what to do now? Should I reinstall with latest NET installer? I already downloaded latest one last night… Cause downloading the DVD installer takes forever on my **** connection. But it appears as if the graphic card is working, already installed the graphic card drivers too, as I see it listed under “Hardware Info” app. Or can I recover this some how?
Or just burn the NET installer to USB stick, and reinstall it all again, hopefully will work and no error at boot after running zypper update.
During installation process, it registered monitor as DVI. I got through to desktop, checked settings for monitor, it listed all these various screen resolutions, and the monitor by model and such. It didn’t do this before with VGA cable. So since I used old DVD installer I then ran Zypper Update, figured I’d let it run while I slept. I woke up to see error at grub loading…
error: file ‘/grub2/i386-pc/normal.mod’ not found.
entering rescue mode…
So not sure what to do now? Should I reinstall with latest NET installer? I already downloaded latest one last night… Cause downloading the DVD installer takes forever on my **** connection. But it appears as if the graphic card is working, already installed the graphic card drivers too, as I see it listed under “Hardware Info” app. Or can I recover this some how?
Or just burn the NET installer to USB stick, and reinstall it all again, hopefully will work and no error at boot after running zypper update.
I recommend starting a new thread for this. A very different problem to the one you started with here. Then wait until you get the appropriate advice. Grub2 configuration can be a tricky process to resolve, depending on the underlying problem
Note that some time a VGA connection may not handshake with the monitor to find it’s resolutions. But they can still be set in xorg.conf
You should not have to reinstall note that it takes the same time and bandwidth to download the files and you don’t have a local copy so I don’t see any advantage in using the net installer.
But in any case this is a different problem and should be put some where someone who knows TW will see
Okay about vga cables, but this is single DVI-D to HDMI cable this time. It registers as DVI, and installed the drivers for the GeForce 210 graphic card during installation process.
This issue is grub issue I’m guessing and there’s more going on here too, this happened other day too, but not grub error/issue, these other errors were there before and are again. I’ll post about it in boot forum. I didn’t try recovery mode yet, but not sure what I’d do anyway? No commands seem to work in rescue boot or whatever. And roger that on the NET installer and DVD installer lol.
I’ve lost track of this thread I’m afraid and don’t feel like going back and reading through it again But I assume your video problems are gone and now you have a grub problem. But that is an entirely different area and since you are using tumbleweed a different group of people need to see the problem. I don’t tumble so need those that do to see the problem which they may not in this thread;)
a buddy sent me this 24" monitor for free (he was just going to junk it or sell it or whatever), and I gave family the original LED monitor I used for so long LED 19" LG Flatron, which didn’t seem to give me much issues at all before. I think I got that one around same time I got the computer parts to build this tower. Of course resolution was like 1366 x 768 something.
Hopefully then get this setup right with all guy’s help. 