Slackware 13 install disk getting stuck at udevd events

onebuck · 09-30-2009, 10:32 AM

Hi,

Sorry, about not getting back to the thread but I've had a few problems that needed attention.

Since you have disconnected both DVD drives and the system booted. I would try using one drive at a time back into the system. Be sure too set the drive jumpers to 'MS' or 'CS'. Check your 'dmesg' to see how things are handled. You may need to update the firmware for the drives. Check your manufacture's website. I think you should place a non-bootable media in the drive to see if that will produce a error, just a thought.

One other thing you could look at is to use the 'generic-2.6.29.6' kernel with a initrd to see if it is possibly a device settling error.

In your 'PM' you stated a problem with your '/etc/lilo.conf'. Please post it. Do you have 'large-memory' in the global section of the '/etc/lilo.conf'?

marcusm · 10-04-2009, 06:39 PM

I disconnected one dvd/cd at a time changing jumpers making each one the master and still the same result.
My lilo setup is, I think, good. It's the same basic setup I used with Slack 12.1 and 12.2 on this system.
For some reason the huge install kernel on Slack 13 is not playing nice with this setup anymore.

So for now, is there a command that I can pass at boot: that would bypass the dvd/cd drives?

ponce · 10-05-2009, 01:50 AM

it still would be nice if you post the lilo.conf you are using

marcusm · 10-05-2009, 11:59 AM

I went in again, by disconnecting the two dvd/cd drives because lilo is booting just fine. I moved the links in /boot to /boot/keepers and reset new ones by doing ln -s So all three links are correctly pointing to System.map, config and vmlinuz for the generic-2.6.29.6 kernel WITHOUT setting up an initrd and booted with no problem. Connecting the dvd/cd drive still results in the very same problem. Thanks for all your patience and help.

Marcus

Here's the lilo setup.

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb6
#compact        # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Append any additional kernel parameters:
append="append=*noapic noudev* vt.default_utf8=0"
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb6
  label = Linux
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

ponce · 10-06-2009, 03:26 AM

I would try modyfing the line

Code:

append="append=*noapic noudev* vt.default_utf8=0"

with

Code:

append=" vt.default_utf8=0"

and relaunch lilo

Code:

# lilo

if this doesn't work add only the noapic option (you can try also at lilo prompt, just write "Linux noapic")

marcusm · 10-09-2009, 03:24 AM

Thanks poncez. I gave all that a good try, and I'm still getting the same results:
hdb: DMA timeout retry
hdb: timeout waiting for DMA

You know, I think it just this !^@#$% Frankenstein of a computer that I rushed to by when compusa closed in my area 1 1/2 years ago. It had this annoying occasional over heating shutdown problem until one day when it crap out on me, just after the warranty ran out. Well, got rid of the crappy video card it came with, used the onboard video and then I had computer a again. Until, now with this Slack 13 install. The thing is, I just finished building a computer for a friend and, this rig only cost $40.00 more then my crappy Frankenstein did and which also, booted the slack 13 install disk like a dream.

Lesson learned; never ever rush to buy a computer no matter what the reason. And always, look beyond the basics: cpu/ram/hd; look at the video card, if any, look at the motherboard and, see how upgradeable it is. Okay, I feel better now.

Back to the problem at hand!

My box now has, two SATA Hard Drives but, the two Optical Drive are IDE. And I'm just realizing, Slackware 12.2 with the 2.6.27.7 kernel installed, booted and ran on this box with no problems until this kernel update for the 2.6.27.31 kernel which is when I really ran into this issue for the first time. At the time 2009-08-18, and now, not having to do any real work in linux for a few years now I couldn't remember but a small hand full of commands and, being that, Slackware 13 with the 2.6.29.6 kernel was on the way, I just decided to wait and take the easy way out. Wait, wait, I'll say it, yea and how did that work out for you Marcus? So I'm wondering, if at all; would this issue be of interest to Patrick Volkerding or to Linus Torvalds.

Current status:
After not being able to boot slack13 install disk, with the help from this forum, I was able to install Slack 13 by using boot: huge.s "noapic noudev"

After trying everything above, I now have the basic lilo.config as above but I cleaned out append and commented it out.

If I disconnect the two IDE Optical Drive this Slackware 13 install does boot with no problems. But awak, no Optical Drive = less fun/less usability.

I've moved the three links in /boot to /boot/keeper and made new one for the generic-smp-2.6.29.6 system, initrd not needed.

Here my box's dmesg | grep -i hd, dmesg | grep -i sd and lspci -vv running slack 12.2 with the 2.6.27.7 kernel

Let me know if I've left anything out. Hoping I gave something more then just my rants.

Marcus.

marcusm · 10-17-2009, 07:17 PM

I'm still trying to resolve this booting issue. I can only boot if I disconnect the two IDE Optical Drive.
I'm starting to think that I'll have to buy two SATA Optical Drive just to get pass this because, I haven't been able,
to find a boot option that allow me to boot with the IDE Optical Drives connected.

If anyone is aware an option that will let me boot with the two IDE Optical Drive connected please post.

best regards,

Marcus.

onebuck · 10-18-2009, 12:25 AM

Hi,

Quote:

Originally Posted by marcusm

I'm still trying to resolve this booting issue. I can only boot if I disconnect the two IDE Optical Drive.
I'm starting to think that I'll have to buy two SATA Optical Drive just to get pass this because, I haven't been able,
to find a boot option that allow me to boot with the IDE Optical Drives connected.

If anyone is aware an option that will let me boot with the two IDE Optical Drive connected please post.

best regards,

Marcus.

Marcus are you still using the M$ bootloader?

If so you can try lilo as the bootloader to see if that's the problem.

I looked through the thread an noticed another issue with your '/etc/lilo.conf' file;

Code:

append="append=*noapic noudev* vt.default_utf8=0"

Should be;

Code:

append = "noapic noudev vt.default_utf8=0"

When you setup the MBR set;

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sdb     <<<-- if that's your boot device

Then run;

Code:

~#lilo -v -t -b /dev/sdb      #set to your device & test
~#lilo -v -b /dev/sdb         #writes to MBR

If you want to use lilo as your boot loader then you can add M$Vista to a stanza then write the lilo again.

I had not gotten a response for this thread activity until a repair on the laptop. I must have missed it while working on other things. Sorry.

BTW, I'm curious to what the motherboard is for the Gateway?

I use IDE & SATA mix all the time on several systems with no problem.

marcusm · 10-18-2009, 02:56 AM

Hi Gary,
Yea, I am using the vista boot loader and it hands over to lilo with no problems. Also, I had noticed that sloppy append entry and had cleaned it up. Lilo does boot about 3/4 through and then it hit the snag at:
hdb: DMA timeout retry
hdb: timeout waiting for DMA

And if I disconnect the two IDE Optical Drive lilo boots the system with no problems.
But wait a minute, we're really talking about the kernel because, once lilo loads the kernel and if used an initrd it's really the kernel that's booting the system, right?

Here's the motherboard: Intel (Schroeder Town) G33 Motherboard

Thanks Gary,

Marcus.

onebuck · 10-18-2009, 02:06 PM

Hi,

Quote:

Originally Posted by marcusm

Hi Gary,
Yea, I am using the vista boot loader and it hands over to lilo with no problems. Also, I had noticed that sloppy append entry and had cleaned it up. Lilo does boot about 3/4 through and then it hit the snag at:
hdb: DMA timeout retry
hdb: timeout waiting for DMA

And if I disconnect the two IDE Optical Drive lilo boots the system with no problems.
But wait a minute, we're really talking about the kernel because, once lilo loads the kernel and if used an initrd it's really the kernel that's booting the system, right?

Here's the motherboard: Intel (Schroeder Town) G33 Motherboard

Thanks Gary,

Marcus.

I think that it was mentioned to use the noprobe option passed to the kernel. You did attempt to pass that? If not try changing your '/etc/lilo.conf' as below then run 'lilo' again.

Code:

append = "noapic noudev hda=noprobe hdb=noprobe vt.default_utf8=0"

Plus, please post the complete 'dmesg' after the re-boot with these options in code tags.