Plarkster Posted February 12, 2004 Share Posted February 12, 2004 I had Fedora Core 1 set up and running nicely, but I've been using Windows for a few days. Now when I boot into Fedora I get this message: modprobe: modprobe: cant locate module block-major-135 135 isn't the only number but they flash by too quickly. I upgraded my graphics card from a Radeon 7500 to a Radeon 9200 yesterday - could this be the problem? Any ideas? Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted February 13, 2004 Veteran Share Posted February 13, 2004 I had Fedora Core 1 set up and running nicely, but I've been using Windows for a few days. Now when I boot into Fedora I get this message:modprobe: modprobe: cant locate module block-major-135 135 isn't the only number but they flash by too quickly. I upgraded my graphics card from a Radeon 7500 to a Radeon 9200 yesterday - could this be the problem? Any ideas? Possibly. What is going on? Does it boot? Text prompt or GUI? Can you get a copy of your dmesg info? Link to comment Share on other sites More sharing options...
Plarkster Posted February 13, 2004 Author Share Posted February 13, 2004 No - it doesnt boot. It starts loading, then switches into text mode and displays this message. I've left it for a few minutes and it doesn't go anything further. How do I get the dmesg info? I used explore2fs to copy the file from bin into windows, but it's scambled so I cant read it. Can I do it another way? Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted February 13, 2004 Veteran Share Posted February 13, 2004 No - it doesnt boot. It starts loading, then switches into text mode and displays this message. I've left it for a few minutes and it doesn't go anything further.How do I get the dmesg info? I used explore2fs to copy the file from bin into windows, but it's scambled so I cant read it. Can I do it another way? Can you get into GRUB and force a runlevel 3 to stay in text mode? Or try singleuser? I'm nost sure what options may be needed to get enough access to what is going on... Perhaps a Knoppix disk? That might work the best, if you can download it or borrow from a friend.... Link to comment Share on other sites More sharing options...
Plarkster Posted February 13, 2004 Author Share Posted February 13, 2004 I've got knoppix, SUSE Live and Slax - I love these live cds! If the dmesg file opens ok I'll post it later. Thanks Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted February 13, 2004 Veteran Share Posted February 13, 2004 Cool. Good Luck! Link to comment Share on other sites More sharing options...
KenLin Posted February 13, 2004 Share Posted February 13, 2004 Here's something I found at Linuxquestions.org: boot up when grub pops up press e use the arrow keys to gotot the second line it should look something like this "kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb" press e again (this enable you to edit the line) change the line to look like this ; "kernel /vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/ rhgb init 3" remove the " 's press enter then press b to boot obviously your kernel version may be different, but just add the init 3 to the end of the line. This will leave you at the command prompt. from there you can edit the /etc/X11/XF86Config file directly or run xF86config Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted February 13, 2004 Veteran Share Posted February 13, 2004 I have always done it by just putting a 3 at the end.... I never tried it with the init 3. Probably is a good idea to be specific when passing things like that to the kernel on boot-up. :yes: One thing that you have to make sure of is that you put a SPACE before you add the 3 (or init 3). You don't want it to become part of the previous parameter. It won't boot that way. ;) Link to comment Share on other sites More sharing options...
kyro Posted February 13, 2004 Share Posted February 13, 2004 exactly of these mod probs , i keep it on init3 when changing hardware Link to comment Share on other sites More sharing options...
Plarkster Posted February 13, 2004 Author Share Posted February 13, 2004 Im nearly done downloading Fedora Core 2 - didn't realise it was out until I was looking for info to fix this. Im gonna upgrade to Core 2 first - is there any chance Core 2 might fix this issue as it may contain a new module for my graphics card (if thats what the problem is)? Link to comment Share on other sites More sharing options...
kyro Posted February 13, 2004 Share Posted February 13, 2004 nice , me also getting Core 2 and to answer 2 Ur question : U better hope this solves the prob. Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted February 13, 2004 Veteran Share Posted February 13, 2004 Just remember FC2 is still in 'beta'.... Should be stable. Should have bugs. (let us know how well it runs!) :yes: Link to comment Share on other sites More sharing options...
Plarkster Posted February 14, 2004 Author Share Posted February 14, 2004 Installed Core 2 and Fedora boots now! I need to have a look at the refresh rate as the screen seems a little fuzzy, but the main problems are that my mouse and sound arent working - both were working fine in Core 1. My mouse is an Intellimouse Explorer (USB) and the soundcard is a Soundblaster Live MP3+. Can anyone help? It's really annoying browsing for answers without a mouse! Link to comment Share on other sites More sharing options...
kemical Posted February 14, 2004 Share Posted February 14, 2004 Installed Core 2 and Fedora boots now! I need to have a look at the refresh rate as the screen seems a little fuzzy, but the main problems are that my mouse and sound arent working - both were working fine in Core 1. My mouse is an Intellimouse Explorer (USB) and the soundcard is a Soundblaster Live MP3+.Can anyone help? It's really annoying browsing for answers without a mouse! check your XF86Config file and see if the mouse is setup properly in that.. you can also change your refresh rate there as well Link to comment Share on other sites More sharing options...
KenLin Posted February 14, 2004 Share Posted February 14, 2004 I upgraded FC1 to the 2.6 Kernel and had exactly those problems. mouse no longer scrolled and no sound at all. Then I found out that lots of people were experiencing exacly these problems and decided to go back to good ol' SuSE 9. :D Link to comment Share on other sites More sharing options...
Plarkster Posted February 14, 2004 Author Share Posted February 14, 2004 I upgraded FC1 to the 2.6 Kernel and had exactly those problems. mouse no longer scrolled and no sound at all. Then I found out that lots of people were experiencing exacly these problems and decided to go back to good ol' SuSE 9. :D I've been thinking the same - I really like SUSE. If Synaptic and apt-get work as well on SUSE as they do on Fedora I'd switch back straight away - have you ever tried it? Link to comment Share on other sites More sharing options...
Plarkster Posted February 14, 2004 Author Share Posted February 14, 2004 check your XF86Config file and see if the mouse is setup properly in that.. you can also change your refresh rate there as well Heres the XFConfig: # XFree86 4 configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection Section "Module" Load "dbe" Load "extmod" Load "fbdevhw" Load "glx" Load "record" Load "freetype" Load "type1" Load "dri" EndSection Section "InputDevice" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option "XkbLayout" "de" # or: # Option "XkbLayout" "de" # Option "XkbVariant" "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps" # Or if you just want both to be control, use: # Option "XkbOptions" "ctrl:nocaps" # Identifier "Keyboard0" Driver "keyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection Section "InputDevice" # If the normal CorePointer mouse is not a USB mouse then # this input device can be used in AlwaysCore mode to let you # also use USB mice at the same time. Identifier "DevInputMice" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "no" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Action Monitor CL-1770" DisplaySize 310 230 HorizSync 30.0 - 70.0 VertRefresh 50.0 - 120.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "radeon" VendorName "Videocard vendor" BoardName "ATI Radeon 7500" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Section "DRI" Group 0 Mode 0666 EndSection Link to comment Share on other sites More sharing options...
KenLin Posted February 14, 2004 Share Posted February 14, 2004 I've been thinking the same - I really like SUSE. If Synaptic and apt-get work as well on SUSE as they do on Fedora I'd switch back straight away - have you ever tried it? Nope. I would be concerned about other package tools causiong inconsistencies in the rpm database, then Yast update might update something it shouldn't. Then again, if you decide to switch to synaptic and ditch the yast update tool, I would think that would work fine. I guess my point is, if you switch to synaptic, stick with it. Link to comment Share on other sites More sharing options...
Recommended Posts