Re: [SLUG] Inserting SIOCSIFADR ..
Yup ! I've got the system up and running again by means of multiple 'make menuconfigs' with the occasional help of System Rescue/Gentoo liveCD's and a number of massive 'dist-upgrades .. and #slug ... except for sound and dependency problems with Gnucash which should resolve themselves as it moves to gtk2/gnome2. I know I've compiled the correct driver for my Creative SoundBlaster audio card into kernel (snd_ens1371), have selected all ALSA options and deselected OSS ones .. but there is something I have missed ... Any ideas ? Adam. [EMAIL PROTECTED] P.S. Thunderbird 1.5 with the BlackJapan theme is impressive ... Michael Fox wrote: SO you got ethernet working? :) On 1/7/06, Adam Felix Bogacki [EMAIL PROTECTED] wrote: Thanks Michael, I ran 'make menuconfig' a number of times until there were no error messages after 'make modules_install' and went through the usual process until after reboot I able to do 'Tux:~# /etc/rcS.d/S40networking start' and go straight into 'apt-get update' and 'apt-get -f upgrade' successfully. The upgrade was big and took a long time. I had noticed some instability on what looked like a malformed screensaver so I kept tapping the spacebar as the upgrade moved into the install phase. At one stage I had to leave the keyboard briefly and on returning found .. [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display END[xxx.xx] rivafb_pan_display END [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display END[xxx.xx] rivafb_pan_display END [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display END[xxx.xx] rivafb_pan_display END [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display START [xxx.xx] rivafb_pan_display END[xxx.xx] rivafb_pan_display END .. covering the screen, [xxx] being digits rapidly cycling upwards. I have been trying various boot parameters to disable 'rivafb' without success, including BOOT_DEBUG=3 debian/installer/framebuffer=false video=vga16:off console=ttys0 console=tty1 Also, the font is really tiny and I've tried to introduce arguments to suit 1024x768 'fb1024' works on the Gentoo-based Rescue CD but not here, neither do variants including 'video=rivafb:1024' or 'rivafb=1024' .. but that is a minor point. I've discovered that 'rivafb' is known to be incompatible with the nvidia driver (I've just used 'nv' previously), and since it is in the kernel the only fix is to 'make menuconfig' - Device Drivers - Graphics - Framebuffer (and disable 'rivafb') before 'make bzImage' and so on. Successive 'init=1' reboots get as far as passwd login before the 'rivafb screensaver' kicks in .. How does one disable it ? Adam. Michael Fox wrote: Modules from another kernel cannot and SHOULD NOT be used with a kernel version it dont match. ie.. if my kernel I am booted too is 2.6.11, then I can only use modules compiled for kernel 2.6.11, I cant copy modules from 2.6.x into the 2.6.11 tree and use them. It dont work like that. I suggest you compile your kernel again and confirm you have selected either the driver to be in the kernel or as a module for your ethernet card. Then issue the usual build process, making sure you also do make modules ; make modules_install, so that any drivers to be modules are compiled and populated into the correct location. On 1/3/06, Adam Felix Bogacki [EMAIL PROTECTED] wrote: Michael Fox wrote: cd /lib/modules ls -l Do you see a dir that matches your currently booted kernel? if so, cd into it and then go hunting in the correct dir for a module relating to network drivers and confirm you can see a matching driver for you tulip card. I had many of those cards some years back.. Thanks Michael .. Tux: /lib/modules# ls 0.0.0 2.4.18-bf2.4 2.4.25-1-686 2.6.14 2.6.5-1-686 Tux: /lib/modules/2.6.14# ls build modules.ccwmap modules.inputmap modules.seriomap source modules.dep modules.isapnpmap modules.symbols kernel modules.alias modules.ieee1394map modules.pcimap modules.usbmap by comparison Tux: /lib/modules/2.6.5-1-686 boot modules.alias modules.ieee1394map modules.pcimap modules.usbmap initrd modules.ccwmap modules.inputmap modules.seriomap kernel modules.dep modules.isapnpmap modules.symbols I copied /kernel/drivers/net/tulip from 2.6.5-1-686 to 2.6.14 and rebooted, to get Tux:~# /etc/rcS.d/S40networking restart /etc/network/options is deprecated grep: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory I noted that /lib.modules/2.6.14 had no 'boot' or 'initrd' directories - so I copied them from 2.6.5 .. but found they were unable to be read in reboot error messages. Tux:/lib
[SLUG] Disabling rivafb at boot ..
Can anyone suggest how to disable ..rivafb.. at boot ? I've unsuccessfully used boot parameters including video=vga16:off console=[device] such as console =ttyc0 console=tty1 Adam. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Inserting SIOCSIFADR ..
Hi, When trying to connect via Tux:~# /etc/rcS.d/S40networking restart I get error messages including SIOCSIFADDR: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device I understand these are kernel modules, although one man page I've seen (to do with Mac's) says that they are now deprecated. I've compiled 2.6.14 - although my earlier kernels seem to have been taken out by an OOPS - and have my original 8 disk Woody 3.0 set using 2.4.* .. Which .deb pkg contains these .. or can you suggest a more elegant way to do this ? Adam [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] OOPS .. contd.
Thanks Daniel,
I'm sorry it's taken so long to reply but I had to get away from
from it all for a while and fight fires on other fronts.
Previously, trying to boot into runlevel 3 I observed a timeout at
INIT: Entering runlevel : 3
Starting system log daemon: syslog
.. after what seemed a long time it reverted to runlevel 1. The same
with 2 and 5.
Daniel Bush wrote:
Adam,
There's not much help I can give. But I've added some comments below.
On 11/29/05, *Adam Felix Bogacki* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I found I had a kernel problem after trying to install
dependencies for
'scribes' in succession when on reboot
I could not get back into my 2.6.5 linux drive.An early error
message was ..
Error inserting genrtc
(lib/modules.2.6.5-1-686/kernel/drivers/char/genrtc.ko): Device or
resource busy.
/etc/init.d/syslog start
.. and later
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
Are you sure there is no way you could get 2.6.5 back up and running
rather than trying to compile and boot a new kernel on an
already-broken system based on 2.6.14 as you tried below?
Good question - and that was was the first area I explored.
Tux:~# mkinitrd /boot/initrd-2.6.5 -o 2.6.5custom
/usr/sbin/mkinitrd: /boot/initrd-2.6.5 is not a valid kernel version
I could not see 2.6.5 or 2.4.14 vmlinuz or linuz images on the system.
Symlinks remained in / or /boot but I could not find the actual files ..
unless I am missing something.
The only working kernels seem to be 2.6.14 and WinXP, on which I write this.
...
After a bit of fiddling with /etc/lilo.conf I finally manged to boot
into my own drive with the following messages
which I reproduce manually in some detail in the hope that they mean
something to someone ..
---
Not running depmod because /lib/modules/2.6.14 is not writable
Loading modules ..
grep: error while loading shared libraries libpcre.so.3: cannot open
shared object file: No such file or directory
FATAL: Could not load /lib/modules/2.6.14/modules.dep: No such
file or
directory
Creating device-mapper files
[screen moves .]
/etc/rc5.d/S19autofs: line33: basename: command not found
...
...
Debian GNU/Linux testing/unstable Tux tty1
Tux login: adam
Password:
-
.. so I was in on tty1 at run-level 1
I quickly found that only my Linux root and WinXP partitions were
auto-mounted - both specified in /etc/lilo.conf
- and I had to manually mount all other partitions except swap
(which I
could not quite work out how to do).
swapon / swapoff
You can use it on files too. (Also see mkswap - not that I think you
need it here, though).
'swapon -a' works, but does not seem to make any difference.
Do you have an /etc/rc.d/rc.sysinit file or similar?
Tux:/# find -name rc.sysinit -print
./opt/ltsp/i386/etc/rc.sysinit
I could not find an /etc/rc.d/rc.sysinit file .. but found many
./etc/rc*.d files, eg /etc/rc0.d, /etc/rcS.d. /etc/rc2.d .. etc.
Hmm .. maybe I could copy ./opt/ltsp/i386/etc/rc.sysinit to /etc/rc.d/
...
You can see how the bootup shell script uses swapon and the 'mount'
command to do stuff (like mounting root dir read-only before going
read-write).
'mount -a' .. worked
Finally,
Tux: /home/adam/linux-2.6.14# make modules_install
if [ -r System.map -a -x /sbin/depmod ] ; then /sbin/depmod -ae -F
System.map 2.6.14; fi
Tux: /lib/modules# ls
0.0.0 2.4.18-bf2.4 2.4.25-1-686 2.6.14 2.6.5-1-686
Tux: /lib/modules/2.6.14# ls
build modules.ccwmap modules.inputmap modules.seriomap source
modules.dep modules.isapnpmap modules.symbols
kernel modules.alias modules.ieee1394map modules.pcimap modules.usbmap
.
As it now stands, I can boot into WinXP on which this is written and
2.6.14 at will
but the latter is text mode (init 1), I have to mount other
partitions
manually,
have no access to the internet preventing a dist-upgrade, and no
X-server.
If you mean runlevel 1, then is your networking script file
('network') in /etc/rc1.d (or similar) prefixed with a K or an S? On
my system it is a 'K' - which means any networking will be killed (an
'S' means it will be started if not already on). Runlevel 1 on my
system has a lot of K's and not a lot of S's. (The shell script file
that manages changes in runlevels on my system is /etc/rc/rc.d.)
Looking at /etc/rc1.d all I seemed to see were K prefixes.
You can start your rc* scripts manually using something like
./XXXnetwork start
[SLUG] OOPS .. 2.6.14 install via Gentoo Live/SysRescue CD
I found I had a kernel problem after trying to install dependencies for 'scribes' in succession when on reboot I could not get back into my 2.6.5 linux drive.An early error message was .. Error inserting genrtc (lib/modules.2.6.5-1-686/kernel/drivers/char/genrtc.ko): Device or resource busy. /etc/init.d/syslog start .. and later Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) .. and a long excerpt starting with grep: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory .. and a lot of '/etc/rc5.d/S20*' messages ending in 'no such file or directory' I found I could log in at tty1 but could not find /home/adam or use vi or vim. I had previously burned a gentoo-based SysRescue CD for resizing partitions and tried to access my dir tree through it. I finally worked out how to do it but could never successfully use 'net-setup eth0' - I've since discovered I was mistakenly entering wrong values. Nevertheless, through it - and later the much more feature-rich Gentoo LiveCD i could get in and look around although I was often confusing the CD fs with my own. Jamie suggested that it could be caused by the initrd missing the device nodes, or kernel modules, required to boot hdb5 (/) .. I could not find an initrd.img file, /var/log/syslog had its last entry on Nov 11, and /var/log/messages ended on July 6. I began to wonder what else I may be missing .. [EMAIL PROTECTED] /boot % ls coffee.bmp debian.bmp debian.lilo.bmp grub lost+found sarge.bmp sid.bmp No sign of /boot/map .. I kept trying mkinitrd but kept getting caught with various error messages. I came to the conclusion that I had to recompile the kernel, but since I had already unpacked the latest kernel - 2.6.14 - in /home/adam I decided to proceed with that with the file system mounted on the Gentoo LiveCD. After menuconfig I successfully did make bzImage and make modules but had problems with 'make modules_install', livecd linux-2.6.14 # make modules_install mkdir: cannot create directory '/lib/modules/2.6.14': Read-only file system make: *** [ _modinst_ ] Error 1 .. which I attributed to its using the CD fs. On reading Linus' kernel release notes I thought of the possibility of bypassing this via [EMAIL PROTECTED] /home/adam/linux-2.6.14/arch/i386/boot cp bzImage /boot/vmlinuz-2.6.14 and re-running LiLo before doing 'modules make_install' from within my own fs I asked on #gentoo whether this was possible without breaking anything - RiverRat assured me it was. After a bit of fiddling with /etc/lilo.conf I finally manged to boot into my own drive with the following messages which I reproduce manually in some detail in the hope that they mean something to someone .. --- Not running depmod because /lib/modules/2.6.14 is not writable Loading modules .. grep: error while loading shared libraries libpcre.so.3: cannot open shared object file: No such file or directory FATAL: Could not load /lib/modules/2.6.14/modules.dep: No such file or directory Creating device-mapper files [screen moves .] /etc/rc5.d/S19autofs: line33: basename: command not found ... grep: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory /etc/rc5.d/S20linuxconf: line 8: /var/run/runlevel.dir: No such file or directory /etc/rc5.d/S20mon: line 32: basename: command not found /etc/rc5.d/S20postgresql-7.4: line 3: /usr/share/postgresql-common/init.d-functions: No such file or directory /etc/rc5.d/S20postgresql-7.4: line 9: start command not found /etc/rc5.d/spampd: line 27: tr: command not found /etc/rc5.d/S20xprint: ##FATAL ERROR: Unknown XProjectRoot. Starting NFS common utilities: statdstatd: Could not chdir: No such file or directory grep: error while loading shared libraries: libpcre.so.3: cannot open shared object file: No such file or directory /usr/sbin/apache is not executable, not starting, reloading ... failed ! Debian GNU/Linux testing/unstable Tux tty1 Tux login: adam Password: - .. so I was in on tty1 at run-level 1 I quickly found that only my Linux root and WinXP partitions were auto-mounted - both specified in /etc/lilo.conf - and I had to manually mount all other partitions except swap (which I could not quite work out how to do). Finally, Tux: /home/adam/linux-2.6.14# make modules_install if [ -r System.map -a -x /sbin/depmod ] ; then /sbin/depmod -ae -F System.map 2.6.14; fi Tux: /lib/modules# ls 0.0.0 2.4.18-bf2.4 2.4.25-1-686 2.6.14 2.6.5-1-686 Tux: /lib/modules/2.6.14# ls build modules.ccwmap modules.inputmap modules.seriomap source modules.dep modules.isapnpmap modules.symbols kernel modules.alias
[SLUG] Re: Kernel panic:
Gerald wrote: On Sat, 19 Nov 2005 06:27 pm, Adam Felix Bogacki wrote: Gerald, I've just downloaded and burned the Gentoo Live CD from ftp://ftp.swin.edu.au/gentoo/experimental/x86/livecd/x86/ thinking it might be more reliable and with more options than the SystemRescueCD. It works nicely but I can't mount partitions from my system because I can't work out the root passwd. It refers to user 'gentoo' with no passwd, but trying to su to 'root' like that did not work, nor did others I tried.. Would you have any ideas on what it could be ? I'm reading up on mkinitrd before trying it .. presumably with the SysRescueCD. Adam Bogacki, [EMAIL PROTECTED] Hello Adam The gentoo boot disk is at root. all you need to do is as follows: 1mount -t ext3(or whatever) /dev/hdax /mnt/gentoo this will mount /dev/hdax on the gentoo root you can then do ls /mnt/gentoo to get a list of the files on that partioion.. If that is not the correct partition do: 2...umount /mnt/gentoo The goto 1 again and try a second partiion If all else fails switch to Gentoo if you have ADSL Best wishes Gerald Yep, you're right. Using /mnt/gentoo I was able to access my own /etc and realised I'd given you incorrect information about my /etc/lilo.conf .. omitting comments and some stuff at the end it looks like lba3 /boot=/dev/hda root=/dev/hdb5 install=/boot/boot-menu.b map=/boot/map delay=150 prompt timeout=175 vga=normal image=/boot/vmlinuz-2.6.5-1-686 label=linux-2.6.5 initrd=/boot/initrd.img-2.6.5custom read-only append=root=/dev/hdb5 image=vmlinuz label=Linux read-only initrd=/initrd.img append=root=/dev/hdb5 image=/vmlinuz.old label=LinuxOLD read-only optional other=/dev/hda1 label= Windows(hda1) .. however my /boot does not contain an 'initrd.img*' file. I have been trying .. livecd root# /usr/sbin/mkinitrd -m /boot/initrd-2.6.5 2.6.5custom .. but keep getting referred to the 'man mkinitrd' file which I've read a few times but can't see the error. What am I missing ? The hyphen ? Re. adsl - I'm using TelstraClear cable - in NZ it's the underdog to Telecom, the local monopolist, and has used creative pricing strategies to take market share, although recently (probably under the influence of the new 'Jefe', Senor Trujillo) prices are going up and download limits reduced ... The Gentoo liveCD kept giving the message The root password on this system has been auto-scrambled for security I could not get into root from the GUI however Ctr-Alt-F1 got me into init 3 as root and I proceeded from there. Adam. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Re: Kernel panic .. Unable to mount root fs
Gerald C. Catling wrote:
hi Adam,
What happend to hdb1?
You should have grub/lilo setting root or real_root to /dev/hdb5
and grub/lilo booting from /dev/hda.
Am i reading you correctly, the boot drive is hdb (one (40G) - the primary
boot drive)
Do you set bios to boot hda- for Windows and hdb- for Linux?
could you copy fstab to me?
Finally have tried to edit the grub/lilo boot screen and try other partitions?
Finally have tried to edit the grub/lilo boot screen and try other partitions?
I run Gentoo 2005.1,mandrake 2006.0 and SuSe 10 all 64bit, i certainly have no
problems compiling the kernel (2.6.13-r6--i think) to run my scsi cd/rw
burner.
Gerald
Thanks Gerald,
below is my /etc/fstab taken from notes after using SystemRescueDisk
to fossick around my file structure.
The SysRescue disk seems to have problems of its own with vi vim
disappearing - I kept getting the message
zsh: command not found vim (a zshell ?) but nano joe still working,
and changing dir to /etc always seemed
to mean *its* /etc and not the mounted one.
To clear up a misunderstanding, I've been running a Debian unstable
system - not Gentoo - but
using a Gentoo-based rescue disk I burned some time ago to use QtParted.
/dev/hda1 /mnt/WinXP
/dev/hdb5 /ext3
defaults,errors=remount-ro
/dev/hdb10 none swap sw
0 0
/dev/hdb2 /boot ext3 defaults
/dev/hdb9 /homeext3
/dev/hdb6 /usrext3
/dev/hdb7 /usr/local ext3
/dev/hdb8 /varext3
/dev/hde5 /home/cyberia ext3
/dev/hde6 /usr/cyberia ext3
.. what happened to /dev/hdb1 ? Dunno .. it was a long time ago and
seemed logical at the time.
You should have grub/lilo setting root or real_root to /dev/hdb5
and grub/lilo booting from /dev/hda.
I use LILO - although have been thinking of changing to GRUB which sits
unpacked ready for use
in /boot.
Extracts from current lilo.conf include
default=Linux
image = /vmlinuz
label=Linux
read-only
restricted
alias=1
image=/vmlinuz.old
label-LinuxOLD
read-only
optional
restricted
alias=2
snip
other=/dev/hda1
label=Windows(hda1)
Am i reading you correctly, the boot drive is hdb (one (40G) - the primary
boot drive)
Yep.
Finally have tried to edit the grub/lilo boot screen and try other partitions?
Not yet - I've been trying to understand the problem ..
Finally have tried to edit the grub/lilo boot screen and try other partitions?
Not yet - as above - but I've spent most of this morning poking around
the partitions.
Following Grant Parnell's comment ..
if you were using LILO it
might have the wrong idea where the blocks for initrd.img are ... but then
again the missing device node idea sounds more plausible - perhaps take
apart the initrd file (its a gzipped ext2 or cpio filesystem usually).
.. I went looking for 'initrd.img' - and could not find it ...
10.01 [EMAIL PROTECTED] / % find -name initrd.img -print
10.01 [EMAIL PROTECTED] / % ls
bin dev home lib opt root tmp var
boot etc initrd mnt proc sbin usr
10.xx [EMAIL PROTECTED] /boot % ls
coffee.bmp debian.bmp debian.lilo.bmp grub
lost+found sarge.bmp sid.bmp
I also noted that the last entry in /var/log/syslog was on Nov 11 and
that /var/log/messages ended on July 6th .. FWIW.
I first noticed the 'kernel panic' msg when doing a 'make install' for
'gnome-python-extras' which should have been routine
but having done a few others immediately before {Python 2.4, PyGTK 2.8 ,
GNOME Python 2.12) I may have struck memory /
kernel limitations which somehow wiped out the 'initrd.img'.
How to create a new initrd.img .. or have I missed something ?
Adam Bogacki,
[EMAIL PROTECTED]
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Kernel panic .. Unable to mount root fs
Hi, despite repeatedly getting error messages saying Error -3 while decompressing ..Md5 stuff. VFS: Cannot open root device hdb5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) .. when I use root=/dev/hdb5 at the root prompt it still happens with both current kernels .. 2.4.25-1 and 2.6.5 .. I either put the expression next to the 'boot:' prompt, or following 'boot: linux.2.* .. same result. Using the Gentoo SystemRescue disk, all filesystems look OK. Syslog shows nothing out of the ordinary (the only FATAL refers to a sound card some time ago), and the boot log dates back to 2003 - not current, but has been like that for some time. Any ideas how I can successfully boot into my Linux drive ? -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Kernel panic .. Unable to mount root fs
Roger Barnes wrote: Hi, despite repeatedly getting error messages saying Error -3 while decompressing ..Md5 stuff. VFS: Cannot open root device hdb5 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) .. when I use root=/dev/hdb5 at the root prompt it still happens with both current kernels .. 2.4.25-1 and 2.6.5 .. I either put the expression next to the 'boot:' prompt, or following 'boot: linux.2.* .. same result. This is probably a long shot, but I'm getting _similar_ problems booting a fresh linux install that was set up on a different machine using a USB chassis. Fingers are currently being pointed at the initrd.img lacking something. Based on the error messages you're getting I'm reasonably sure that's not the problem for you (though I'm just learning all this boot stuff myself), but it might be a lead worth following. The next step in my situation is to create a new initrd.img with some extra modules in it. HTH, - Roger Thanks, I'll have a look at it. Adam. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Can't reboot: cannot open /mnt/etc/fstab: no such file
Hi, using Debian unstable I did an 'apt-get dist-upgrade --fix-missing'
last night and on
booting this morning found login now had audio, and that the post-login
screen had remembered
theme, font-sizes, and other details from my last session. So far so
good - I was impressed.
But when I chose metacity as windows manager and deleted the first
(config) screen
as normal after using it, things started going wrong.
I could not move or use the second gnome-terminal opened at login. It
had no top
border, and clicking it did not give it focus meaning that I could not
enter text.
After some effort I decided that I could not do anything with it and
rebooted.
I don't like doing this but have found that the system can usually recover
after some time. In retrospect, maybe I should have logged out.
On reboot, the kernel loads normally, but them I get the following boot-log
message, followed by the iterated sequence ...
...snip.
hdb: irqtimeout: status=0xd0 {Busy}
ide0: reset: success
...snip
I'd be grateful for any constructive advice.
Adam Bogacki,
[EMAIL PROTECTED]
[Transcribed boot-log follows.]
[hda: is my WinXP drive]
hda: DMA disabled
hdb: drive not ready for command
ide0: reset: success
blk: queue d732fa00, I/O limit
/scripts/ext3: add-journal.sh: 30: cannot open /mnt/etc/fstab: no such file
EXT-fs: INFO: recovery required on readonly filesystem
EXT-fs: write access will be enabled during recovery
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
ide: reset: success
hdb: irq timeout: status=0xd0 {Busy}
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Boot hangs at 'Starting Samba daemons: nmbd smbd'
Hi, I did an 'apt-get dist-upgrade --fix-missing' yesterday which at the install phase 'hung' on the message Starting Samba daemons: nmbd smbd ... dselect 'c' installed the rest but I found that reboot 'hung' on rsync daemon not enabled in /etc/default/rsync Starting Samba daemons: nmbd smbd ... until reboot.. I tried booting from the mkinitrd image but it stalled at the same message. Is this a known bug ? I have heard something about about rsync being buggy in unstable (if that's relevant). Google assumes you can first boot in and then do things as root. Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] [Success] Re: Root: mkinitrd ... Permission denied. (?)
Thanks - it worked. Unfortunately, the cursor is fixed in the middle of the screen. The 'Input Device' section of /etc/X11/XF86Config-4 uses '/dev/psaux' and '/dev/mouse' and replacing either with' /dev/input/mice' or ' /dev/psmouse' causes X to crash. Modprobe has no reaction to the 'mousedev' and 'psmouse' modules, but tells me that module 'psaux' is not installed. I'll have to try try 'insmod psaux lp' ... Is this a known 2.6.5 kernel config problem ? Adam Bogacki, [EMAIL PROTECTED] Adam Felix Bogacki wrote: Hi, at the risk of being tiresome (to myself if no one else) ... [...] VFS: Cannot open root device hdb5 or unknown-block (0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown block (0,0) Googling around has suggested that 2.6.5 has changed the parsing of the root= boot argument. No, there is no change in root argument. Of course you can define your partitions on different ways. Are you sure that your root device is hdb5 and maybe not hda5? Tux:~# /usr/sbin/mkinitrd -m /boot/initrd.img-2.6.5-1-686 -o 2.6.5custom /usr/sbin/mkinitrd line 1: /boot/initrd.img-2.6.5-1-686: Permission denied What am I missing here ? Wrong options. Usage: /usr/sbin/mkinitrd [OPTION]... -o outfile [version] -m is for setting a command to make the image You should not need it. mkinitrd -o /boot/initrd.img-2.6.5custom 2.6.5-1-686 should be right for you... -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Re: Root: mkinitrd ... Permission denied. (?)
Sorry Bob, you are right. It was nearing 1.00 AM and I was a bit tired and emotional with things going wrong. Apologies, Adam Bogacki, [EMAIL PROTECTED]. Bob Proulx wrote: Adam, Did you mean to post this to [EMAIL PROTECTED] instead of to us at [EMAIL PROTECTED]? GNU coreutils are the basic file, shell and text manipulation utilities of the GNU operating system. You don't seem to be having a GNU coreutils problem. I suggest looking there first. http://lists.debian.org/debian-user/ Bob Adam Felix Bogacki wrote: Hi, at the risk of being tiresome (to myself if no one else) ... I apt-graded to kernel-image-2.6.5-1-686 successfully, but after the next dist-upgrade - which 'upgraded' the kernel-image - I found reboot gave me kernel panic "VFS: Cannot open root device "hdb5" or unknown-block (0,0) Please append a correct "root= " boot option Kernel panic: VFS: Unable to mount root fs on unknown block (0,0)" Googling around suggested that 2.6.5 has changed the parsing of the "root= " boot argument. I rebooted with the rescue disk (2.4.8-bf2.4), which is missing its modules dependency file (modules.dep), but now find "Tux:~# /usr/sbin/mkinitrd -m /boot/initrd.img-2.6.5-1-686 -o 2.6.5custom /usr/sbin/mkinitrd line 1: /boot/initrd.img-2.6.5-1-686: Permission denied" Am I missing something here - or a bug ? Adam Bogacki, [EMAIL PROTECTED] ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-coreutils -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Root: mkinitrd ... Permission denied. (?)
Hi, at the risk of being tiresome (to myself if no one else) ... I apt-graded to kernel-image-2.6.5-1-686 successfully, but after the next dist-upgrade - which 'upgraded' the kernel-image - I found reboot gave me kernel panic VFS: Cannot open root device hdb5 or unknown-block (0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown block (0,0) Googling around suggested that 2.6.5 has changed the parsing of the root= boot argument. I rebooted with the rescue disk (2.4.8-bf2.4), which is missing its modules dependency file (modules.dep), but now find Tux:~# /usr/sbin/mkinitrd -m /boot/initrd.img-2.6.5-1-686 -o 2.6.5custom /usr/sbin/mkinitrd line 1: /boot/initrd.img-2.6.5-1-686: Permission denied Am I missing something here - or a bug ? Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Re. Kernel panic: 2.6.5.-1-686 boot probs.
Thanks guys. I've googled by 'mkinitrd examples', 'dave jones 2.6 upgrade' 'wonderful world of 2.6' - which explains (i.a.) that parsing of the 'root= ' command has been altered in 2.6.5 - but in trying to get past 'Kernel panic' with a newly installed 2.6.5-1-686 kernel by booting off a 2.4.18-bf2.4 rescue disk I get the following error message: Tux:~# /usr/sbin/mkinitrd -m /boot/initrd-2.6.5-1-686custom.img -o 2.6.5custom /usr/sbin/mkinitrd: /lib/modules/2.4.18-bf2.4: Not a directory /usr/sbin/mkinitrd: MODULES needs to be set to none ? Tux:~# cd /lib modules Tux:~# /lib/modules ls 0.0.0 2.4.25-1-686 2.6.5-1-686 modprobe.conf modprobe.conf.old My initial system was 2.4.18-bf2.4, I upgraded to 2.4.25*, and later to 2.6.5* The disk is almost certainly 2.4.18-bf2.4 ... What do I have to do to successfully boot the 2.6.5* kernel ? Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Re. Kernel panic: 2.6.5.-1-686 boot probs.
Thanks Alex. What was your fix ? I can't get past the 'Kernel Panic' message using 2.6.5* and at the moment cannot access the net using the rescue floppy with a 2.4* kernel. Cheers, Adam. On Mon, May 10, 2004 at 09:26:39PM +1200, Adam Felix Bogacki wrote: Thanks. I've been googling by the last line of the error message "Kernel panic: VFS: Unable to mount root fs on unknown-block (3,69)" I received this error when I first went to 2.6.x it was caused by the change in the initrd modules, check which version of mkinitrd you have and weather it matches the kernel version you have. A -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Re. Kernel panic: 2.6.5.-1-686 boot probs.
Thanks. I've been googling by the last line of the error message Kernel panic: VFS: Unable to mount root fs on unknown-block (3,69) It seems that a common problem with various 2.6 kernel versions exists with locating their root partitions, eg. when your boot entry says 'root=/dev/hdb5' (eg. mine) these kernels construct an incorrect path, resulting in kernel panic. Different fixes are proposed. One suggestion was to change the root line into something like 'root=0305' (where, apparently, '03' stands for hda - perhaps identifying the third drive, what XP calls ':C') and the '05' is the partition number. In my case that would be 'root=0405' - but that did not get past 'kernel panic'. All the symlinks in /boot appear to be there. Another suggestion is to add 'append=root=/dev/hdb5' to the image sections of lilo, but that did not work either. When I ran lilo I received /dev/mapper/control: open failed: no such device Is device-mapper driver missing from kernel ? /dev/mapper/control: open failed: no such device Is device-mapper driver missing from kernel ? Incompatible libdevmapper 1.00-15-ioctl (2004-04-07) (compat) and kernel driver Warning: The boot sector and map file are on different disks. Added Linux* ... Another fix is based on the fact that if vmlinuz is not pointing to the new kernel, it is a waste of time. This can be fixed by using a live CD Knoppix variant, booting, and mounting /usr/ and /var by hand to proper mount points. I can boot from the rescue floppy using a 2.4* kernel, but cannot access the net *** how can Paradise static cable be configured here ? *** which might allow me to change '/etc/apt/sources.list' to 'testing' and 'dist-upgrade'. I have tried mount /dev/hdb6 /mnt/hdb5/usr mount /dev/hdb8 /mnt/hdb5/var but keep getting the message that it is not a proper mount point. One is then supposed to chroot /mnt/hdb5 (whatever is correct), edit lilo.conf, and then run lilo. Another fix is to append root=/dev/hdb5/3,69or /(3,69), or just /3 or root=/dev/345/3 (?) but I'm not sure which option (if any) is correct here. The /boot partition is about 80% full at the moment and I don't think that sizing is a factor right now. My notes show that within /boot 'initrd.img-2.6.5-1-686' has gone from 4571136 to 4009984, in other words it has decreased in size from my first (successful) install of 'kernel-image-2.6.5-1-686' to after I did a dist-upgrade. That's a change of 561152. I may have a partly installed package here. I have tried to move and resize /boot (within 1024 blocks), but Parted keeps giving me a message along the lines that it is possible but may cause trouble in certain circumstances. I don't know how seriously to take this with unstable. I'd appreciate any constructive advice. Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Kernel panic: 2.6.5.-1-686 boot probs.
Thanks Greg. Adam, Have you got: initrd=/initrd.img in your lilo.conf file? Yep. If you can boot with another kernel why don't you just put in the old 2.6.5 kernel (it is in /var/cache/apt/archives) Thanks, I found it. But how do I do that ? your mouse problem with XFree86 and 2.6.X kernel is all over the net. Just search in google. The quick fix is something like this: edit /etc/X11/XF86Config-4 find a line that has /dev/psaux or /dev/usb/mouse0 or similar replace with /dev/input/mice and restart X. WhenI did that X would not start. I have two entries in separate paragraphs under 'pointing device' (or whatever), 'dev/psaux' and '/dev/input/mice' ... changing the first crashes X. snip. Also I try and keep the last working kernel at /vmlinuz.old so I can always boot from that if I get into trouble. ... is there a symlink from /vmlinuz.old to /var/cache/apt/archives ? ...but more importantly, I keep getting the message Error -3 While decompressing ! c0355f8c(1027641439)-d7c2(4096) VFS: Cannot open root device 345 or unknown-block (3,69) Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on unknown-block (3,69) and the boot process hangs. lilo.conf (attached) has boot=/dev/hda root/dev/hdb5 but neither of them, or 'root=/dev/hda1' work in allowing the boot process to continue. There must be a simple solution. [Sorry about the graphic mess below. I transcribed it by hand from Linux to XP drives, as I had no cut paste. It looked OK in Moz-Thunderbird] Any ideas ? Adam Bogacki, [EMAIL PROTECTED] On Sun, 2 May 2004 08:40 pm, Adam Felix Bogacki wrote: Oops, I forgot to run lilo ... but I then got the error message /dev/mapper/control: open failed: No such device Is device mapper driver missing from kernel ? Incompatible libdevmapper 1.00.15-ioctl (2004-04-07) (compat) and kernel driver Warning: The boot sector and map file are on different disks Added Linux * Skipping /vmlinuz.old Added DOS when I try to reboot from C: using the newly installed apt-upgraded kernel I get Error -3 While decompressing ! c0355f8c(1027641439)-d7c2(4096) VFS: Cannot open root device 345 or unknown-block (3,69) Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on unknown-block (3,69) Tux:~# df Filesystem1K-blocks Used AvailableUse Mounted on /dev/hdb5 13690082183251079997 17% / tmpfs1919800 191980 0% /dev/shm /dev/hda119991104 10655424 9335680 54% /mnt/DOS /dev/hdb2 7746 6970376 95% /boot /dev/hdb9 18951504 372340814265404 21% /home /dev/hdb6 12342396 1934112 9781352 17% /usr /dev/hdb718729604358641341916 25% /usr/local /dev/hdb818247682984081433588 18% /var /dev/hde5 7692876 8 7302092 1% /home/cyberia /dev/hde6 1344016 8 1275736 1% /usr/cyberia ... previously /boot was showing 100% full. Tux:/boot# ls . -la system.map-2.6.5-1-686 787887 lost+found 1024 boot.0300 512 map 73728 vmlinuz-2.6.5-1-686 1125072 config-2.6.5-1-686 52167 initrd.img-2.6.5-1-686 4009984 and four symlinks range: 31-34 The boot error message makes reference to an unknown block. This may be due to my use of 'parted' to increase space in /usr which was previously 99% full. This was successful, but my attempt to increase the size of /boot was not - I'm at a loss to understand why. [EMAIL PROTECTED] /root % parted /dev/hdb snip Information: The operating system thinks the geometry on /dev/ide/host0/bus0/target1/lun0/disc is 4865/255/63. Therefore, cylinder 1024 ends at 8032.499M (parted) print -snip- Disk label type: msdos Minor Start End Type Filesystem Flags 20.031 7.844 Primaryext3 boot 17.844 38162.219 extended 5956.997 2337.583 logical ext3 7 2384.679 4243.732 logical ext3 8 4290.8296102.817 logical ext3 9 6196.979 32153.532logical ext3 6 32247.694 37244.443 logical ext3 10 37244.474 38162.219logical ext3 (parted) resize 2 0.03125.567 [trying to enlarge /boot] Warning: You requested to resize the partition to 0.031-25.567Mb. The closest Parted can manage is 0.031-7.844MB. I understand that Parted is choosing options consistent with interactions between firmware and software, but it has previously stated that ...cylinder 1024
[SLUG] After kernel 2.6.5-1 install, cursorprinting lost, reboot hangs after upgrade...
Hi, attempting to installing MPlayer, I found had no audio with the 2.4.18-bf2.4 kernel. I apt-installed the 2.4.25-1-686 kernel, headers, and alsa-modules but was ultimately informed on alsa-users that my kernel/modules were 'foobar' . Kernel 2.6 .5-1-686 includes alsa-modules so I tried that. On first reboot, I found that OO0 1.1 and AbiWord would not print but that MPlayer had good audio and video, when it worked. On subsequent reboots, the cursor was frozen in the center of screen following login but I could use command-line functions in unconfigured windows, including mutt and MPlayer. I tried a number of 'apt-get updates' and 'apt-get dist-upgrades --fix-missing' in the hope that appropriate package downloads would fix the cursor and problems. The last 'dist-upgrade --fix-missing' included an upgrade of 'kernel-image-2.6.5-1-686' and the install of a 'libmouse' package, but then came a message that modules needed to be re-generated during boot, and that I needed to 'reboot soon'. On rebooting however, I get the message "Loading Linux .." and then the screen hangs. I can access the system on a 2.25 kernel rescue disk, but which does not have net access. I'd like to fix this problem so I can get on with the rest of my life. Any constructive ideas ? Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Kernel panic: 2.6.5.-1-686 boot probs.
Oops, I forgot to run lilo ... but I then got the error message /dev/mapper/control: open failed: No such device Is device mapper driver missing from kernel ? Incompatible libdevmapper 1.00.15-ioctl (2004-04-07) (compat) and kernel driver Warning: The boot sector and map file are on different disks Added Linux * Skipping /vmlinuz.old Added DOS when I try to reboot from C: using the newly installed apt-upgraded kernel I get Error -3 While decompressing ! c0355f8c(1027641439)-d7c2(4096) VFS: Cannot open root device 345 or unknown-block (3,69) Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on unknown-block (3,69) Tux:~# df Filesystem1K-blocks Used AvailableUse Mounted on /dev/hdb5 13690082183251079997 17% / tmpfs1919800 191980 0% /dev/shm /dev/hda119991104 10655424 9335680 54% /mnt/DOS /dev/hdb2 7746 6970376 95% /boot /dev/hdb9 18951504 372340814265404 21% /home /dev/hdb6 12342396 1934112 9781352 17% /usr /dev/hdb718729604358641341916 25% /usr/local /dev/hdb818247682984081433588 18% /var /dev/hde5 7692876 8 7302092 1% /home/cyberia /dev/hde6 1344016 8 1275736 1% /usr/cyberia ... previously /boot was showing 100% full. Tux:/boot# ls . -la system.map-2.6.5-1-686787887 lost+found 1024 boot.0300 512 map 73728 vmlinuz-2.6.5-1-686 1125072 config-2.6.5-1-686 52167 initrd.img-2.6.5-1-686 4009984 and four symlinks range: 31-34 The boot error message makes reference to an unknown block. This may be due to my use of 'parted' to increase space in /usr which was previously 99% full. This was successful, but my attempt to increase the size of /boot was not - I'm at a loss to understand why. [EMAIL PROTECTED] /root % parted /dev/hdb snip Information: The operating system thinks the geometry on /dev/ide/host0/bus0/target1/lun0/disc is 4865/255/63. Therefore, cylinder 1024 ends at 8032.499M (parted) print -snip- Disk label type: msdos Minor Start End Type Filesystem Flags 20.031 7.844 Primaryext3 boot 17.844 38162.219 extended 5956.997 2337.583 logical ext3 7 2384.679 4243.732 logical ext3 8 4290.8296102.817 logical ext3 9 6196.979 32153.532logical ext3 6 32247.694 37244.443 logical ext3 10 37244.474 38162.219logical ext3 (parted) resize 2 0.03125.567 [trying to enlarge /boot] Warning: You requested to resize the partition to 0.031-25.567Mb. The closest Parted can manage is 0.031-7.844MB. I understand that Parted is choosing options consistent with interactions between firmware and software, but it has previously stated that ...cylinder 1024 ends at 8032.499Mb so that there should be plenty of room to increase the size of /boot, given that it should be placed lower than cylinder 1024. In any case, the size of /boot may not be the reason for the boot process failing. What would be a correct root= boot option ? I have unsuccessfully tried the option boot: /dev/hdb5 . What am I missing here ? I'm currently reduced to tweaking my DOS drive ... Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Help ! Kernel setup stack overlaps LILO second stage
Hi, Running a routine 'update' and 'dist-upgrade' in unstable I found today that 'kernel-image-2.4.25-1-686' and associated files such as 'kernel-headers' were to be upgraded. I had previously found 'alsa-modules-2.4.25-1-686' would not install because a number of modules (the four files quoted in error messages had names ending in '.so') had "characters which could not be resolved". I assumed (hopefully) that this could have fixed this.. At the end of the dist-upgrade I was told that reboot was necessary. I did so but found that the LILO screen had the message "Lilo 22.5.8 (Debian) Boot menu ...snip. boot: Loading Linux EBDA is big; Kernel setup stack overlaps LILO second stage." 'df' had shown my /usr partition to be 100% but I thought I may be able to sneak through after deleting 'ppp' associated files - I use cable on this system. I surmise that I should get in there and delete, delete, delete ... and try again. But I can't - I'm stuck with the same LILO error message whenever I try to reboot. I have had to send this message from my unused Win partition - a bit like going back in time. Any constructive ideas appreciated. Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Re: Font problem
Yep, I've got xfonts-100dpi, xfonts-100dpi-transcoded, xfonts-75dpi, xfonts-75dpi-transcoded, xfonts-artwiz, xfonts-base, xfonts-base-transcoded ... as well as gsfonts-x11, and a few others. That's not the problem. I'm a bit bemused by an apparently missing x font server in /etc/X11 ... surely Debian (unstable) still uses it ? Adam Bogacki, [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
