Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
"Alert /dev/sda4 does not exist" and drop to busyboxI compiled a custom kernl 2.6.23.1. When I try to boot I get "Alert /dev/sda4 does not exist" and it drops to busybox shell. My /boot/grub/menu.list ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.23.1-custom title Debian GNU/Linux, kernel 2.6.23.1-custom (single-user mode) title Debian GNU/Linux, kernel 2.6.18-4-686 title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode) ### END DEBIAN AUTOMAGIC KERNELS LIST my /etc/stab: # /etc/fstab: static file system information. lsusb I hope someone can help because I need the 2.6.23 kernel to get my wireless to work. Thanks Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
"Alert /dev/sda4 does not
The "mkinitramfs" script might have left off a driver. When busybox comes up, check to see what drivers have loaded and find out why you don't have /dev/sda - the possibilities are:
1. driver didn't load (or at least the SCSI layer driver didn't load)
2. devices were renamed - sda is now sdc or something like that - I doubt this because the udev scripts should have ensured that the name doesn't change.
If it's a missing driver, boot to the old kernel and rebuild the initramfs image - but first edit /etc/initramfs-tools/modules and put in the name of the missing module.
There are a few ways to rebuild the initramfs image; the easiest (if you used the Debian build scripts) is:
dpkg-reconfigure whatever-your-kernel-package-is.deb
Otherwise read the 'mkinitrd' manual pages to see how it needs to be invoked.
"Alert /dev/sda4 does not
Thanks for the reply. Which of these modules is for the hard drive?
lsmod
Module Size Used by
rfcomm 34584 0
l2cap 21696 5 rfcomm
bluetooth 45956 4 rfcomm,l2cap
ipv6 226016 14
ppdev 8676 0
parport_pc 32132 0
lp 11012 0
parport 33256 3 ppdev,parport_pc,lp
button 6672 0
ac 5188 0
battery 9636 0
via_agp 9664 0
agpgart 29896 1 via_agp
dm_snapshot 15552 0
dm_mirror 19152 0
dm_mod 50232 2 dm_snapshot,dm_mirror
loop 15048 0
tsdev 7520 0
joydev 9088 0
snd_hda_intel 17332 1
snd_hda_codec 137856 1 snd_hda_intel
snd_pcm_oss 38368 0
snd_mixer_oss 15200 1 snd_pcm_oss
snd_pcm 68676 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
zd1211rw 38304 0
snd_timer 20996 1 snd_pcm
firmware_class 9600 1 zd1211rw
snd 47012 8 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
ieee80211softmac 26304 1 zd1211rw
ieee80211 29416 2 zd1211rw,ieee80211softmac
serio_raw 6660 0
soundcore 9248 1 snd
snd_page_alloc 9640 2 snd_hda_intel,snd_pcm
rtc 12372 0
ieee80211_crypt 5952 1 ieee80211
psmouse 35016 0
pcspkr 3072 0
i2c_viapro 8244 0
shpchp 33024 0
pci_hotplug 28704 1 shpchp
i2c_core 19680 1 i2c_viapro
evdev 9088 1
ext3 119240 1
jbd 52456 1 ext3
mbcache 8356 1 ext3
sd_mod 19040 3
ide_cd 36064 0
cdrom 32544 1 ide_cd
sata_via 10052 2
libata 89396 1 sata_via
scsi_mod 124168 2 sd_mod,libata
via_rhine 22664 0
mii 5344 1 via_rhine
ehci_hcd 28136 0
generic 5476 0 [permanent]
via82cxxx 8388 0 [permanent]
ide_core 110504 3 ide_cd,generic,via82cxxx
uhci_hcd 21164 0
usbcore 112644 4 zd1211rw,ehci_hcd,uhci_hcd
thermal 13608 0
processor 28840 1 thermal
fan 4804 0
pjharper@gUn:~$
"Alert /dev/sda4 does not
Is that from your system that boots or the one that doesn't? You have all the drivers in there:
scsi_mod
sd_mod
libata
sata_via
It is possible that the drivers don't load in the order you want and your disk is 'hda' instead of 'sda'. You can check easily with fdisk:
fdisk -l /dev/sda
(Assuming the busybox version of fdisk works that way).
Fatal Modprobe not found
Yes the lsmod was from my working system with a stock Etch kernel.
I did the cat /proc/modules
All of the above are missing. I tried "modprobe libata" and modeprobe sata_via" but I get Fatal module not found.
Perhaps I need to recompile my kernel. I used make oldconfig but I guess it failed to install the modules.
fdisk -l /dev/sda found nothing. No surprise there.
Recompiling
It looks like I forgot the modules :(
So back to compiling
Recompiling
I recompiled. Still does not work.
In Single User Mode it fails with:
usb 4-5: configuration #1 chosen from 1 choice
scsi_mod has loaded this time.
fdisk and cfdisk both are not there.
Recompiling
gUn:~# update-initramfs -ctk linux-image-2.6.23.1-custom
update-initramfs: Generating /boot/initrd.img-linux-image-2.6.23.1-custom
Cannot find /lib/modules/linux-image-2.6.23.1-custom
update-initramfs: failed for /boot/initrd.img-linux-image-2.6.23.1-custom
Recompiling
In your case this should be:
update-initramfs 2.6.23.1
Recompiling
I recompiled and found that for some reason I keep missing the modules:
libata
sata_via
Where do I find them in menuconfig?
Recompiling
You may not have the modules because you selected 'y' rather
than 'm' - in some cases this makes the system work
differently from what you intended (unless you can pass extra
parameters to ensure that other in-kernel drivers initialize
first).
Look in the .config file you use for compiling.
A lot of the SATA code is still in 'EXPERIMENTAL', so you
need to locate CONFIG_EXPERIMENTAL and set that to:
CONFIG_EXPERIMENTAL=y
Now when you do an 'oldconfig' it should ask you questions about the experimental features.
Also if you go to the section for CONFIG_ATA, you should see
entries like
CONFIG_SATA_VIA=m
CONFIG_ATA_GENERIC=m
(just examples - the drivers you need to activate depends on your system)
Recompiling
Pinniped you have pointed me in the right direction. I compiled a good kernel and the zd1211rw module is in there.
iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
Warning: Driver for device eth1 has been compiled with version 22
of Wireless Extension, while this program supports up to version 20.
Some things may be broken...
And the end of dmesg
zd1211rw 1-5:1.0: zd_usb_init_hw()
usb 1-5: request_fw_file() fw name zd1211/zd1211b_ub
usb 1-5: Could not load firmware file zd1211/zd1211b_ub. Error number -2
zd1211rw 1-5:1.0: couldn't load firmware. Error number -2
zd1211rw 1-5:1.0: zd_usb_init_hw()
usb 1-5: request_fw_file() fw name zd1211/zd1211b_ub
usb 1-5: Could not load firmware file zd1211/zd1211b_ub. Error number -2
zd1211rw 1-5:1.0: couldn't load firmware. Error number -2
zd1211rw 1-5:1.0: zd_usb_init_hw()
usb 1-5: request_fw_file() fw name zd1211/zd1211b_ub
usb 1-5: Could not load firmware file zd1211/zd1211b_ub. Error number -2
zd1211rw 1-5:1.0: couldn't load firmware. Error number -2
eth1 Interface doesn't support scanning : No such device
Still not sure what is wrong :(
Recompiling
Have you installed the package 'zd1211-firmware' ?
Recompiling
No. It looks like I need the .deb from:
http://zd1211.wiki.sourceforge.net/VendorBasedDriver or
"With Debian you can optionally use the zd1211-firmware and zd1211-source packages from the unstable or testing distributions."
Recompiling
The firmware is available as a Debian package - what is in your /etc/apt/sources.list ?
You can see if it's in your current repository list:
apt-cache search zd1211
The driver is also part of the kernel, so you don't need to compile it separately unless you have a newer chip which is supported by the latest driver but not the driver in your current kernel.