LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices



Reply
 
Search this Thread
Old 11-30-2007, 11:31 AM   #1
radiodee1
Member
 
Registered: Oct 2006
Location: New York
Distribution: Debian
Posts: 673
Blog Entries: 11

Rep: Reputation: 36
console resolution at boot up conflicts with modem?


I've been trying to get 1024x768 at boot up and for my consoles. Everything works fine, and the computer boots up fine. I log in but when I try to use the onboard modem by typing 'pon' there is some sort of error. The modem will actually start dialing, then at about half way through dialing it stops. Then there's a message from syslogd in the xterminal or console (it doesn't matter which) and then a whole lot of text scrolls down the screen. This text doesn't stop, the keyboard freezes, and the computer needs to be rebooted. Strangely the mouse keeps working. I cannot switch to a console, or, if I am in a console I cannot switch back. The following is my grub entry:

Code:
kernel          /boot/vmlinuz-2.6.22-2-k7 root=/dev/sda7 ro noapic nolapic vga=791
I use a conexent internal modem. The driver comes from a company called linuxant. The driver is in the form of a deb package, but of course I didn't get it using apt-get and linuxant isn't in my sources.list. Below is some of the error message that I could copy by hand or with the mouse:

Quote:
Message from syslogd@howdy at Fri Nov 30 05:44:13 2007 ...
howdy kernel: general protection fault: 0000 [#1]

Message from syslogd@howdy at Fri Nov 30 05:44:13 2007 ...
howdy kernel: SMP

Message from syslogd@howdy at Fri Nov 30 05:44:13 2007 ...
howdy kernel: CPU: 0

Message from syslogd@howdy at Fri Nov 30 05:44:13 2007 ...
howdy kernel: EIP: 0060:[<c0104b05>] Tainted: PF VLI

Message from syslogd@howdy at Fri Nov 30 05:44:13 2007 ...
howdy kernel: EFLAGS: 00010002 (2.6.22-2-k7 #1)

(more of same...)
This part streams down the screen and repeats itself over and over until I must restart the computer.

Quote:
cnxthsf_OsEventWaitTime(f6c9c720/HDA CodecUnsolicitedMessage, 40): returning OSEVENT_WAIT_TIMEOUT
cnxthsf_OsEventWaitTime(f6c9c720/HDA CodecUnsolicitedMessage, 40): returning OSEVENT_WAIT_TIMEOUT
(more of same...)
Does anybody else have one of these modems, or can anyone advise me on an easy way to solve a problem like this. I suppose I could just stay away from 1024x768 for the console. I don't know if it matters but I use the fglrx driver for my video card. Any help would be appreciated. Thanks in advance.

Last edited by radiodee1; 11-30-2007 at 11:34 AM.
 
Old 11-30-2007, 01:40 PM   #2
acummings
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 615

Rep: Reputation: 49
Quote:
an easy way to solve a problem like this
Use an external modem on a com port, say com 1 or com 2

These external modem can be had used for not much cost if you ebay shop or elsewise have access to surplus computer store and/or computer store.

Linux likes hardware modem, especially likes external modem on com port.

If your internal is a "Win" modem then these can difficulty to work with Linux.

--
Alan.
 
Old 11-30-2007, 02:10 PM   #3
radiodee1
Member
 
Registered: Oct 2006
Location: New York
Distribution: Debian
Posts: 673
Blog Entries: 11

Original Poster
Rep: Reputation: 36
Thanks for the quick reply. I neglected to mention this is a laptop. I don't think I have a com 1 or com 2. Also, the modem works with the linuxant software, just not if I pass 'vga=791' as a kernel parameter. Any other ideas?
 
Old 12-01-2007, 02:40 AM   #4
acummings
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 615

Rep: Reputation: 49
/boot/grub/menu.lst

next snippet is from above file

title Debian GNU/Linux, kernel 2.6.18-5-686
root (hd0,1)
kernel /boot/vmlinuz-2.6.18-5-686 root=/dev/sda2 ro vga=0x317
initrd /boot/initrd.img-2.6.18-5-686
savedefault

------------------------------------------------------

Mine's a desktop. It didn't like the other form of vga=

(that's why the hex) in mine -- I guess it's hex that I'm using -- I do not know why it didn't like the digits form

Oh, I don't know much -- maybe it's not hex in mine. I *did* have to experiment with it for some time just in order to get frame buffer working like it does now for me. (default Etch for me was very huge terminal screen fonts without frame buffer). I now have near or do have 1024x768 frame buffer in terminal.

-----------------------------------------------------

Wierd that modem and frame buffer (have anything) to do with each other.

----------------------------------------------

3com or usrobotics pcmcia card modem ???

-------------------------------------

I'd do the pcmcia card thing on my (old) IBM Thinkpad 600E laptop rather than to get its onboard modem working in Linux. But I don't need a modem so I've never fiddled with same on my laptop.

-------------------------------------------------

--
Alan.
 
Old 12-01-2007, 08:01 AM   #5
radiodee1
Member
 
Registered: Oct 2006
Location: New York
Distribution: Debian
Posts: 673
Blog Entries: 11

Original Poster
Rep: Reputation: 36
I don't know who makes the modem. The laptop is Dell, and the ordering info says the modem is integrated into the network card, which I can tell is Broadcom from lspci. BTW, I tried the 'vga=0x317' too, with the same result. It is hex. I kind-of like having the modem 'internal' and don't need 1024x768 on the consoles so badly, so I'll probably just do without the high resolution. I did read somewhere something about irq's though, and think they might be my problem. Which irq my console uses and which irq my modem uses, and how to change one of them, though, is beyond me. If anybody knows, that would be great.
 
Old 12-01-2007, 10:17 AM   #6
makuyl
Senior Member
 
Registered: Dec 2004
Location: Helsinki
Distribution: Debian Sid
Posts: 1,107

Rep: Reputation: 53
It's also possible that you have a memory mapping conflict.
If it's irq's, try pci=biosirq or some other kernel parameters affecting interrupts.
 
Old 12-01-2007, 04:01 PM   #7
radiodee1
Member
 
Registered: Oct 2006
Location: New York
Distribution: Debian
Posts: 673
Blog Entries: 11

Original Poster
Rep: Reputation: 36
What does one do about memory mapping conflicts. How does one even detect them? I tried 'pci=biosirq' and 'irqfixup' but neither one worked.

EDIT: I also tried 'irqpoll'. That didn't work either.

Last edited by radiodee1; 12-01-2007 at 05:33 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Console Boot up in higher resolution xmnemonic Linux - Software 5 02-01-2004 12:55 AM
modem and mouse conflicts dwdrumman75 Linux - Hardware 0 01-21-2004 06:16 PM
console resolution on boot ixefs Linux - General 1 12-21-2003 04:10 PM
Modem Conflicts nunativs Linux - Hardware 2 10-20-2003 10:04 PM
setting console boot resolution Gill Bates Linux - Newbie 2 09-10-2003 03:54 PM


All times are GMT -5. The time now is 10:58 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration