Hello,

I'm trying to install slackware64-current by creating a usb boot stick using the instructions in the USB & PXE folder in the current folder.

I've created a USB boot device using

"dd if=usbboot.img of=/dev/sda bs=512"

Upon boot it starts off well but seems to hang at this line:

"Triggering udev events /sbin/udevadm trigger"

Have tried remaking usb stick with no affect.
Can anyone advise what the problem might be.
Is there any other info I could provide that would be helpful?

No idea why udev is causing you trouble. Can you try adding the keyword "noudev" (without typing the quotes) to the command that boots you into the installer? The full line you need to type goes like this:
It will instruct the installer not to use udev and instead rely on the old Slackware way of initializing the hardware (which means you will have to rung the "network" program to probe for your network card prior to running "setup", if you are going to do a network install).

Eric

Hey, as a follow-up to this issues I've final managed to get Slackware64-current installed on an LVM partition and create an initrd.gz.

However I had to use the noudev option no matter what boot media I used and now udev seems to be causing further issues. When I boot my new installation slackware hangs at precisely the same point. (Upon first reboot there were some further messages about acpi, though they don't appear anymore).

I'm now stuck with a system I can't boot in order to fix it. I don't know what udev is and why it's causing these problems.

How can boot my system and then fix / bypass this udev issue?

I will ask PiterPUNK (our UDEV maintainer) to check out this thread, and to see if he has any troubleshooting tips for you.
There will probably be many questions to provide data/reports/screenshots/logs/whatever. I understand that if a computer does not boot, it will be hard to provide logs. But using the Slackware installer with the "noudev" commandline boot-option, you will be able to get into your computer with enough tools available to satisfy the needs of those who want information.

Good luck, Eric

I suspect that there's some module being loaded that your system doesn't like for whatever reason.

Hope you get it sorted, James.

I have the same problem with slackware 13 on my acer one.
I try boot with a usb stick and with a external usb dvd drive.
In these two ways i have the same issue that the 250GB sata unit is not found.

I tryed to boot from a 12.2 slackware and now the same problem.

When i tryed to boot from a 12.1 slackware, for my surprise, the HD was founded under /dev/hda!

So, can anybody say why the earlier version of slackware works and the newest don´t??

Ismael.

PS.: Can i install the 12.1 version and then upgrade to the 13? How make this upgrade?

@ faiscaheisler - did you try adding "noudev" on the commandline when you boot the USB installer and see if Slackware detects your drive then? If you add "noudev", then Slackware will not use udev to look for devices, and instead use the "old" trusted setup scripts (the same scripts that are also in Slackware 12.1).

Eric

I tried with huge.s and hugesmp.s
Also tried with many combinations of noacpi, noudev, nomsi, acpi=off, hda=noprobe options but the HD is not detected.

If it helps, lspci command says that i have a Intel IDE SCH Poulsbo interface and the HD is a Hitachi sata.
The netbook is a Aspire One AO751h-1340.

Today i tryed a install with one Ubuntu 9.04 iso and it works fine.

Ismael.

Hi,

Try passing the 'noapic' along with the 'noudev' at the boot of the installer.

BTW, I suggest that you stay within your original thread. I really believe your problem is not the same as this thread. Some association but your seems different. Diagnosis would be easier if contained within your original thread.