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.
|
 |
01-01-2005, 04:39 PM
|
#1
|
Member
Registered: Dec 2004
Location: Alemania
Distribution: Slackware 10.0
Posts: 115
Rep:
|
PCTV->No boot
Hi there!
Happy new year to all of you!
I am running Slack 10.0 and today I installed my Pinnacle PCTV Pro. Winshit works... but then I tried to boot Slackware... and wham! Stops while hotplugging or something. No booting anymore!
I stops with this errors, which tell me absolutly nothing!:
Error-Pic
Only thing I can do ist STRG+Alt+Del ...
I tried to boot Damn Small Linux (like Knoppix) and it booted like it should. But this does not fix anything :-) Just nice to know...
Can someone tell me how to get around this? Any help is welcome!
Greetings, Sascha
Last edited by Cornholio; 01-01-2005 at 04:41 PM.
|
|
|
01-01-2005, 06:08 PM
|
#2
|
LQ Guru
Registered: Jan 2002
Posts: 6,042
Rep: 
|
I think your ramdisk has ext3 and jbd modules loaded which can give you problems like the one shown because it did for me. To fix this, use Knoppix or any LIVE LINUX CD and mount the boot partition or any partition that contains /boot directory. Next decompress initrd.gz with gzip. Then mount initrd as a loop device. Fourth, find the file load_kernel_modules in the loop device and load it up in a text editor. Comment jbd and ext3 lines by placing # in the beginning of each line. Unmount the loop device or image file and use gzip to compress initrd. Then reboot the computer. Slackware should then work.
BTW, modules in the ramdisk file have to be decompress in order for it to be loaded by busybox (a universal Linux program that can run as a certain program depending on the name of symbolic link).
|
|
|
01-02-2005, 04:50 AM
|
#3
|
Member
Registered: Dec 2004
Location: Alemania
Distribution: Slackware 10.0
Posts: 115
Original Poster
Rep:
|
Hi there!
This sounds like a plan ... thanks very much so far!
But what I didn't get by now is, what exactly the error is?
Thanks again, greetings - Sascha
|
|
|
01-02-2005, 06:36 AM
|
#4
|
Member
Registered: Dec 2004
Location: Alemania
Distribution: Slackware 10.0
Posts: 115
Original Poster
Rep:
|
Ok... I tried it out some minutes ago... but I ran into problems.
First of all my initrd was not zipped ... not really a problem I think. But...
Can't mount it. Not because of an error ... more because I don't know how to do this ...
I mounted the hd where my /boot is on. Then I moved to "/mnt/hdb2/boot". Next I tried to mount it somewhere:
mount -o loop initrd /mnt/cdrom
But I was told I should give a filesystem.
mount -o loop -t ext3 initrd /mnd/cdrom
was my try. Ext3 is the FS I use on my Slackware box. But that didn't work. I was told I chose the wrong fs-type or something like that.
Can you give me a hint with that?
Something else, that came up my mind ... if I remember right, I didn't have an initrd until I added a bootsplash to my Box ... is that possible? If so, does that make any changes to your tip?
Thanks again, Sascha
|
|
|
01-02-2005, 03:45 PM
|
#5
|
LQ Guru
Registered: Jan 2002
Posts: 6,042
Rep: 
|
The ramdisk file or initrd is ext2. If you do not know the filesystem, use auto. It takes more time for the kernel to detect the filesystem but it is smart picking the right filesystem.
The ramdisk file or initrd is not really needed if the filesystem you are using is compiled in the kernel instead being as a module.
Probably the error is the module ext3 is duplicating it self in memory, but I do not have enough experience in Linux to verify this.
|
|
|
01-02-2005, 04:16 PM
|
#6
|
LQ Guru
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
|
Just a guess but maybe hotplug does not under stand the new card correctly or is not compatiable with current modules. If hotplug is setup this way, one can add ' bttv ' to the blacklist at /etc/hotplug/blacklist. I am guessing it is trying to use this one. It might be using something else but not my area of knowledge.
Brian1
" Google the Linux way @ http://www.google.com/linux "
|
|
|
All times are GMT -5. The time now is 08:54 PM.
|
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
|
|