Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
05-11-2003, 06:22 PM
#61
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
Ok, here is what happned:
boot: root=/dev/hda1
Could not find kernel image: root=/dev/hda1
And yes, it is hda1
Was i supposed to type:
boot: bare.i root=/dev/hda1
Last edited by DiZASTiX; 05-11-2003 at 06:23 PM .
05-11-2003, 06:25 PM
#62
Senior Member
Registered: Sep 2001
Location: Brisvegas, Antipodes
Distribution: Slackware
Posts: 4,590
Rep:
Post the output of 'fdisk -l /dev/hda'.
05-11-2003, 06:38 PM
#63
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
Its in a table but im writing it like this:
Device: /dev/hda1
Boot: *
Start : 1
End" 807
Blocks: 6100888+
Id: 83
System: Linux
Device: /dev/hda3
Boot:
Start : 808
End" 833
Blocks: 196560
Id: 82
System: Linux Swap
And no, there is no hda2
05-11-2003, 06:47 PM
#64
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
I tried:
boot: bare.i root=/dev/hda1
and it boots into my regular linux off the hd and not the cd, but the sound doesnt work
Yet, im not sure if it is using the new kernel?
*edit*
Also if it helps, this is my current /etc/lilo.conf (the one i used on my last recompile)
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="opl3=0x388"
boot = /dev/hda1
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz.old
root = /dev/hda1
label = slack
read-only
# Linux bootable partition config ends
Last edited by DiZASTiX; 05-11-2003 at 06:50 PM .
05-11-2003, 06:56 PM
#65
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
I was thinking, even though i booted from the cdrom, hda1, maybe it is not using the new compiled kernel. Like, if i had lilo running, it would let me choose, so maybe when i boot hda1 from the cdrom it is using the old kernel?
*edit*
I just found out that i cannot make a boot disk, the kernel is too big
So i need to fix LILO or get the CDRom to boot the new compiled kernel off hda1
Last edited by DiZASTiX; 05-11-2003 at 07:41 PM .
05-11-2003, 07:42 PM
#66
Member
Registered: Mar 2003
Location: Everett
Distribution: Slackware
Posts: 805
Rep:
This
# Linux bootable partition config begins
image = /boot/vmlinuz.old
root = /dev/hda1
label = slack
read-only
# Linux bootable partition config ends
Should look like this
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = slack
read-only
image=/boot/vmlinuz.old
root=/dev/hda1
label=linux
read-only
# Linux bootable partition config ends
05-11-2003, 07:59 PM
#67
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
quietguy: i just tried that but the sound doesnt work, im booting by puting in the cdrom and saying:
boot: bare.i root=/dev/hda1 noinitrd ro
Would this help, this is one part i get when i type dmesg:
Kernel command line: initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_s IMAGE=/kernels/bare.i/bzImage root=/dev/hda1 noinitrd ro
Also, lilo still gives me LI
05-11-2003, 08:06 PM
#68
Member
Registered: Mar 2003
Location: Everett
Distribution: Slackware
Posts: 805
Rep:
You corrected your /etc/lilo.conf file?
05-11-2003, 08:14 PM
#69
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
Yes. Here is the new one
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="opl3=0x388"
boot = /dev/hda1
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = slack
read-only
image=/boot/vmlinuz.old
root=/dev/hda1
label=linux
read-only
# Linux bootable partition config ends
05-11-2003, 08:14 PM
#70
Member
Registered: Mar 2003
Location: Everett
Distribution: Slackware
Posts: 805
Rep:
I'm wondering if you may need the lowmem.i kernel. bare.i maybe be to big after compiling.
05-11-2003, 08:16 PM
#71
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
On my earlier post, where it says :
IMAGE=/kernels/bare.i/bzImage
The /kernels/bare.i/bzImage is from the CD Just to let you know.
05-11-2003, 08:17 PM
#73
Member
Registered: Mar 2003
Location: Everett
Distribution: Slackware
Posts: 805
Rep:
bare.i is the default Slackware kernel.
05-11-2003, 08:31 PM
#74
Member
Registered: Mar 2003
Location: Everett
Distribution: Slackware
Posts: 805
Rep:
I must be stupid. I should have told you to run /sbin/lilo this time after modifying lilo.conf
05-11-2003, 08:41 PM
#75
Member
Registered: Mar 2003
Location: Boston Area
Distribution: Ubuntu (Edgy)
Posts: 247
Original Poster
Rep:
Ok, i ran it i got:
Warning: LBA32 addressing assumed
Added slack *
Added linux
Then i rebooted and booted from the cd
boot: bare.i /dev/hda1 noinitrd ro
And logged in, started X but the sound still doesnt work
BTW I dont have lowmem.i on the cd, i only have these:
adaptec.s
bare.i
jfs.s
raid.s
scsi.s
scsi2.s
speakup.i
xfs.i
idk why the sound wont work, when i compiled and made slack i did everything!
All times are GMT -5. The time now is 11:35 AM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News