On Wed, 20 Nov 2024 19:22:25 +
Andy Smith wrote:
> Sounds interesting and useful. I think you should write an article on
> your blog, make sure that is archived in web.archive.org, and also put
> the essentials of it in an article on the Debian Wiki.
Thank you. That is what I will do, then.
On Thu, 21 Nov 2024 11:47:41 +0200
Anssi Saari wrote:
> One rescue system I like, grml, has a Debian package
> grml-rescueboot which does this for their images. The package
> provides a longish /etc/grub.d/42_grml to do its thing.
Thanks, I'll take a look at it.
--
Does anybody read signatures
Charles Curley writes:
> I've developed a script and suitable grub stanzas to let the user
> install several CD-ROM images on a hard drive, and boot from the
> CD-ROMs without extracting the kernel or initrd. This gives the user
> something of a rescue capability without requ
On Wed, 20 Nov 2024 15:46:01 -0500
Stefan Monnier wrote:
> IIUC in your case, they can each use their
> own partitions.
Currently, they all reside on the same partition. I suppose a bit of
hacking could put each on its own. An interesting thought. But that's
more work than I want to do right now
>> In the past I've used the `grub-imageboot` package for that.
> Near as I can tell, somewhere along the line the kernel and initrd are
> extracted from the (CD|DVD|diskette) image.
IIUC `grub-imageboot`s boot entries boot the ISOs by running the
`memdisk` program, passing it the ISO. I don't re
On Wed, Nov 20, 2024 at 06:44:50PM +0100, Thomas Schmitt wrote:
> Hi,
[...]
> At similar occasions i created pages in the Debian wiki and asked the
> general public for review and comments:
[...]
noted.
Cheers
--
t
signature.asc
Description: PGP signature
Hi Charles,
On Wed, Nov 20, 2024 at 10:21:09AM -0700, Charles Curley wrote:
> I think this might make a useful how-to, possibly for the Debian wiki.
> Any thoughts on where to contribute it?
Sounds interesting and useful. I think you should write an article on
your blog, make sure that is archive
On Wed, 20 Nov 2024 13:01:35 -0500
Stefan Monnier wrote:
> In the past I've used the `grub-imageboot` package for that.
Aha! Thank you.
Near as I can tell, somewhere along the line the kernel and initrd are
extracted from the (CD|DVD|diskette) image. My software doesn't even
require that. Grub
Hi,
> I've developed a script and suitable grub stanzas to let the user
> install several CD-ROM images on a hard drive, and boot from the
> CD-ROMs without extracting the kernel or initrd.
> ...
> I think this might make a useful how-to, possibly for the Debian wiki.
> A
> The three images I have been working with are recent netinst weekly
> builds, a recent Finnix, and the gparted live CD. All three go on their
> own partition, in hope that that partition would isolate them from file
> system catastrophes.
Nice. In the past I've used the `grub-imageboot` package
I've developed a script and suitable grub stanzas to let the user
install several CD-ROM images on a hard drive, and boot from the
CD-ROMs without extracting the kernel or initrd. This gives the user
something of a rescue capability without requiring a CD/DVD or thumb
drive.
The three ima
On Wed, Nov 20, 2024 at 10:21:09AM -0700, Charles Curley wrote:
> I've developed a script and suitable grub stanzas to let the user
> install several CD-ROM images on a hard drive, and boot from the
> CD-ROMs without extracting the kernel or initrd. This gives the user
> some
Sounds interesting, I would really like to give it a try.
kworm InRelease
> Err:2 cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD
> Binary-1 with firmware 20230610-10:23"] bookworm Release
> Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update
> cannot be used to add new CD-ROMs.
> Reading pac
e, tty1
I re-inserted the USB drive and based on the guide titled Use ISO image as
CD-ROM repository in Ubuntu (url:
https://techpiezo.com/linux/use-iso-image-as-cd-rom-repository-in-ubuntu/), I
did the following:
1. sudo mkdir -p /mnt/mount-iso
2. sudo mount -o loop /dev/sda1 /mnt/mount-iso
3
On 7/29/22 12:11, Schwibinger Michael wrote:
Thank You.
Is this neccessary
Only you can decide how to allocate your resources -- knowledge, skills,
spare parts, spare computers, tools, equipment, time, money, etc..
Trouble-shooting is both an art and a science. Given some undesirable
iss
Thank You.
Is this neccessary
when there is already a button HP 600?
Regards
Von: David Christensen
Gesendet: Freitag, 29. Juli 2022 18:46
An: debian-user@lists.debian.org
Betreff: Re: Linux cannot find CD Rom
On 7/28/22 23:46, Schwibinger Michael wrote
On 7/29/22 10:48, Schwibinger Michael wrote:
Extern is fine
intern is bad.
Re-seat the CD drive power cable, data cable, and motherboard end of
data cable. Swap the CD drive data cable with a known good cable.
Remove the CD drive and test with known good computer.
David
On 7/28/22 23:46, Schwibinger Michael wrote:
Hello
I try to open a CD.
But Linux cannot find it.
How can I repair it.
No light
no reaction during putting CD in.
On 7/29/22 08:03, Schwibinger Michael wrote:
> Its HP Deskjet
> Do You need more?
>
> Internal drive
>
> Debian 11
>
> USB Drive is
Thank You
Extern is fine
intern is bad.
Regards Sophie
I can open it
so there is electricity.
Von: rhkra...@gmail.com
Gesendet: Freitag, 29. Juli 2022 15:38
An: debian-user@lists.debian.org
Betreff: Re: AW: Linux cannot find CD Rom
On Friday, July 29, 2022
On Friday, July 29, 2022 11:05:41 AM Schwibinger Michael wrote:
> Put CD into the USB external drive.
>
> No problem.
Is the external USB drive the drive you are having trouble with? If so, it
sounds like you have a media problem -- the media you are using is not
suitable for the drive. (Or,
Betreff: Re: Linux cannot find CD Rom
On Friday, July 29, 2022 07:51:59 AM Richard Owlett wrote:
> On 07/29/2022 01:46 AM, Schwibinger Michael wrote:
> > Hello
> > I try to open a CD.
> > But Linux cannot find it.
> What hardware are you using?
> Is the CD drive i
2 11:51
An: debian-user@lists.debian.org
Betreff: Re: Linux cannot find CD Rom
On 07/29/2022 01:46 AM, Schwibinger Michael wrote:
> Hello
> I try to open a CD.
> But Linux cannot find it.
> How can I repair it.
> No light
> no reaction during putting CD in.
> Thank You
> Reg
On Friday, July 29, 2022 07:51:59 AM Richard Owlett wrote:
> On 07/29/2022 01:46 AM, Schwibinger Michael wrote:
> > Hello
> > I try to open a CD.
> > But Linux cannot find it.
> What hardware are you using?
> Is the CD drive internal or external?
> What "Linux" are you using? This list is for Debi
On 07/29/2022 01:46 AM, Schwibinger Michael wrote:
Hello
I try to open a CD.
But Linux cannot find it.
How can I repair it.
No light
no reaction during putting CD in.
Thank You
Regards
Sophie
What hardware are you using?
Is the CD drive internal or external?
What "Linux" are you using? This li
Hello
I try to open a CD.
But Linux cannot find it.
How can I repair it.
No light
no reaction during putting CD in.
Thank You
Regards
Sophie
Hi,
jeremy bentham wrote:
> eject: unable to eject, last error: Inappropriate ioctl for device
The inappropriate ioctl() does not necessarily have to be the reason
of the failure. man 1 eject indicates that several methods are tried.
> The command sees the drive (it's not the quietest thing i
Using the eject command I get the following message:
eject: unable to eject, last error: Inappropriate ioctl for device
This is new: I used the drive to install the OS (jessie? Debian 9, anyway)
and I've actually--not too recently--listened to a CD on it.
Feeding The Duck the message didn't h
The drive also does not respond to the physical control on the
case.
--
Dave Williamsd...@eskimo.com
On Wed 16 May 2018 at 00:35:33 (+0200), Pascal Hambourg wrote:
> Le 15/05/2018 à 03:23, David Wright a écrit :
> >
> >In this particular instance (the Lenovo), its PDF says:
> (...)
> > The default boot mode for your computer is UEFI mode. If you need to
> > install a legacy operating syste
Hi,
Mike Kupfer wrote:
> there seems to be something odd going on with the live image ISOs.
> [...]
> alto$ sudo dd if=debian-live-9.4.0-amd64-xfce.iso of=/dev/sdb bs=32K
> [...]
> 1951465472 bytes (2.0 GB, 1.8 GiB) copied, 455.702 s, 4.3 MB/s
> alto$ sudo isosize -x /dev/sdb
> sector co
Thomas Schmitt wrote:
> Mike Kupfer wrote:
> > I used sha256sum instead of sha512sum, but I otherwise followed
> > the above instructions. The checksum from the dd pipeline does not
> > match the checksum of the original .iso file.
>
> That's not good.
> Especially we do not have to show up at g
Le 15/05/2018 à 03:23, David Wright a écrit :
In this particular instance (the Lenovo), its PDF says:
(...)
The default boot mode for your computer is UEFI mode. If you need to
install a legacy operating system, such as Windows (that is, any operating
system before Windows 8)
Hi,
Mike Kupfer wrote:
> I used sha256sum instead of sha512sum, but I otherwise followed
> the above instructions. The checksum from the dd pipeline does not
> match the checksum of the original .iso file.
That's not good.
Especially we do not have to show up at grub-devel as long as the test
US
On Mon 14 May 2018 at 23:29:43 (+0200), Pascal Hambourg wrote:
> Le 14/05/2018 à 02:02, David Wright a écrit :
> >On Sun 13 May 2018 at 19:08:48 (+0200), Pascal Hambourg wrote:
> >>
> >>Most of my early experience with UEFI boot comes from a rather old
> >>Intel motherboard. Beside crippled UEFI su
On Mon 14 May 2018 at 11:56:11 (-0400), Stefan Monnier wrote:
> > Yes, documentation of firmware is almost unknown in my experience
> > (since probably 30 years ago). That's why I took the least invasive
>
> It's documented to the extent that it says "implements UEFI" and that
> UEFI is documented
Chris Ramsden wrote:
> On 2018-05-14 01:21, songbird wrote:
>> Pascal Hambourg wrote:
>> ...
>>> I agree with the author. If you want to keep the existing EFI Windows
>>> installation and have a convenient dual boot with GRUB, you'll have to
>>> set up your favourite distribution to boot in EFI m
Mike Kupfer wrote:
> Since the OP's problems were with 9.4, I haven't tried a more recent
> ISO, but I'll download an image and test it. (If this turns out to be
> fixed in 9.4, I will be very embarrassed and will happily buy y'all
> a meal if you're ever in the Bay Area.)
I just tried 9.4, usin
Thomas Schmitt wrote:
> Mike Kupfer wrote:
> > If I plug the stick into the laptop when it's running, the stick is
> > mounted okay. [...] didn't notice anything odd, but then I'm not familiar
> > with the contents of a hybrid image ISO.
>
> They have about the best verification support you can w
Le 14/05/2018 à 02:02, David Wright a écrit :
On Sun 13 May 2018 at 19:08:48 (+0200), Pascal Hambourg wrote:
Most of my early experience with UEFI boot comes from a rather old
Intel motherboard. Beside crippled UEFI support (no UEFI boot from
USB or SATA in AHCI mode), it had a couple of annoyi
Thomas Schmitt wrote:
> Does the live image always succeed and the netinst image always fail ?
> Is always the same USB stick affected ? (Or do you have one for each ISO ?)
> How do you actually "select" between installer and live ?
I made some changes between the initial attempts and what I'm do
Hi,
David Wright wrote:
> I read it as meaning that the USB stick works as a live system
> (first boot), but not as an installer (second boot).
Hm ... re-reading Mike's mails ...
Mike Kupfer wrote in his first mail:
> > > using a netinst image and a live image.
and today:
> > If I select the in
On Mon 14 May 2018 at 18:13:08 (+0200), Thomas Schmitt wrote:
> Hi,
>
> Mike Kupfer wrote:
> > I'm booting using EFI.
>
> So this could be a problem with GRUB about how it leaves the USB stick
> after having loaded kernel and initrd from it.
>
> The volatility of success and failure still gives
Hi,
Mike Kupfer wrote:
> I'm booting using EFI.
So this could be a problem with GRUB about how it leaves the USB stick
after having loaded kernel and initrd from it.
The volatility of success and failure still gives me riddles. But if you
can reproduce failure within a bearable number of tries,
> Yes, documentation of firmware is almost unknown in my experience
> (since probably 30 years ago). That's why I took the least invasive
It's documented to the extent that it says "implements UEFI" and that
UEFI is documented.
>> Same here (basically for the same reason: the behavior of the firm
On 2018-05-14 14:55, David Wright wrote:
> Would I be correct in thinking that the BIOS POST boot screen is
> what you get when you hit F12 sufficiently quickly after switch-on?
> So are you choosing between UEFI and Legacy (compatibility) mode.
> (I would like to know how Dell handles what I've be
time it worked (live image boot). I then tried
rebooting and running the installer, and it failed in the usual place.
> > [!!] Detect and mount CD-ROM
> > No common CD-ROM drive was detected.
>
> This does not match the complaint in the web to which
On Mon 14 May 2018 at 09:14:23 (-0400), Stefan Monnier wrote:
> > That said, there are other statements that are odd:
>
> Not sure what you find odd about them:
>
> > "I really can’t recommend strongly enough that you do not attempt
> > to mix UEFI-native and BIOS-compatible booting of
>
On Mon 14 May 2018 at 13:28:56 (+0100), Chris Ramsden wrote:
> On 2018-05-14 01:21, songbird wrote:
> > Pascal Hambourg wrote:
> > ...
> >> I agree with the author. If you want to keep the existing EFI Windows
> >> installation and have a convenient dual boot with GRUB, you'll have to
> >> set up
> That said, there are other statements that are odd:
Not sure what you find odd about them:
> "I really can’t recommend strongly enough that you do not attempt
> to mix UEFI-native and BIOS-compatible booting of
> permanently-installed operating systems on the same computer, and
>
On 2018-05-14 01:21, songbird wrote:
> Pascal Hambourg wrote:
> ...
>> I agree with the author. If you want to keep the existing EFI Windows
>> installation and have a convenient dual boot with GRUB, you'll have to
>> set up your favourite distribution to boot in EFI mode. If you want to
>> go
gt; This prompted me to go back to try to reproduce the CD-ROM thing. And
> yes, I can reproduce a failure that sounds like the one that was
> originally reported.
> [!!] Detect and mount CD-ROM
> No common CD-ROM drive was detected.
This does not match the c
Pascal Hambourg wrote:
...
> I agree with the author. If you want to keep the existing EFI Windows
> installation and have a convenient dual boot with GRUB, you'll have to
> set up your favourite distribution to boot in EFI mode. If you want to
> go back to legacy boot, including for Windows, yo
On Sun 13 May 2018 at 19:08:48 (+0200), Pascal Hambourg wrote:
> Le 13/05/2018 à 17:18, David Wright a écrit :
> >On Fri 11 May 2018 at 15:13:04 (-0500), Kent West wrote:
> >>
> >>That's good to know. I guess my source material (
> >>https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-
r writing data.
>
> We shall note that this is not what Kent West, the OP, reports for his
> problems. If his problem is hardware related, then it is more fuzzy
> than yours.
This prompted me to go back to try to reproduce the CD-ROM thing. And
yes, I can reproduce a failure that sounds
Hi,
Mike Kupfer wrote:
> (full files sent off-list)
Received.
> Hmm. The bad log has
>
> [7.015708] usbcore: registered new interface driver uas
> [ 25.552030] random: crng init done
It is quite sparse from that point on:
[ 29.034207] usb 1-2: reset high-speed USB device number 2
Le 13/05/2018 à 17:18, David Wright a écrit :
On Fri 11 May 2018 at 15:13:04 (-0500), Kent West wrote:
That's good to know. I guess my source material (
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
is wrong. Or I misunderstood it.
While a lot of the de
Thomas Schmitt wrote:
> Mike Kupfer wrote:
> > I have a copy of kern.log from the first (successful) boot, and I have
> > the dmesg output from the second (failed) boot. If anyone wants to look
> > at them, let me know.
>
> I am interested. Especially whether there are messages from the ISO 966
On Fri 11 May 2018 at 15:13:04 (-0500), Kent West wrote:
> On Fri, May 11, 2018 at 2:59 PM, Pascal Hambourg
> wrote:
>
> > Le 11/05/2018 à 20:33, Kent West a écrit :
> >
> >>
> >> I learned that EFI boot drives need to have a GPT partition table. On a
> >>
> >
> > This is not correct. The UEFI sp
Hi,
i wrote:
> > The messages quoted by Kent could well indicate that the "CD-ROM" was
> > found
Curt wrote:
> I was laboring under another erroneous impression for some reason, but
> looking back at the OP he did say that the installer complained about
> not bein
cdrom;
>
> The messages quoted by Kent could well indicate that the "CD-ROM" was found
> but that rather a particular file was not readable or did not yield the
> expected checksum.
I was laboring under another erroneous impression for some reason, but
looking back at the OP he
essages from the ISO 9660
filesystem driver.
Curt wrote:
> I've mounted usb sticks that spontaneously 'umounted' themselves while
> producing similar I/O reset errors.
> Which might conceivably explain why the installer would begin asking for
> the cdrom;
The messages
Hi,
Pascal Hambourg wrote:
> I have never seen a hard disk or flash drive with a sector size of 2048
> (only 512 or 4096) so the kernel must be correct and the Apple partition
> table must be wrong.
Both are correct. The kernel reports what it perceives as hardware block
size ("physical"). The Ap
On 2018-05-13, Mike Kupfer wrote:
>
> usb 1-2: device descriptor read/64, error -110
> ...
> usb 1-2: reset high-speed USB device number 2 using xhci_hcd
>
> I tried booting from a different USB port; that worked once, but on a
> subsequent attempt it failed with the same issue.
>
I've moun
Le 12/05/2018 à 21:38, Thomas Schmitt a écrit :
Pascal Hambourg wrote:
Why then does parted complain about a block size discrepancy ?
Because the Apple Partition Map announces to count blocks with size 2048
whereas the Linux device file announces 512 (via ioctl(BLKSSZGET) ?)).
I already kno
Kent West wrote:
> I have a Dell Latitude E7250 laptop. I'm trying to install Debian to it using
> a USB stick.
[...]
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read
> the CD-ROM.
ttps://packages.debian.org/stretch/load-cdrom
This package is not to see as file in the ISO.
It could be that there is no problem with finding the "CD-ROM" but rather
with installing or activating that package. So maybe it could not even
begin its work.
About its role in debian-installer
Le 11/05/2018 à 22:38, Thomas Schmitt a écrit :
Pascal Hambourg wrote:
It also has Apple and GPT partition tables, but they are bogus
The GPT is not valid because there is a non-"protective" MBR partition
table. The APM is valid, but should be of no interest for any firmware
that does not exp
Le 12/05/2018 à 01:04, Rick Thomas a écrit :
After doing the cp or dd to write the .iso to the USB, do you do a “sync”
before you eject it?
I don't, because I don't feel the need to.
According to its man page description, sync "flush file system buffers",
but the destination is a raw device,
nents. At this point it gets
>about a quarter of the way through then throws big error message saying:
>
> *[!!] Load installer components from CD*
>
> There was a problem reading data from the CD-ROM. Please make sure it is in
> the drive. If retrying does not work., you shoul
eem to recognize the trackpad (which is
> recognized in the laptop's EFI firmware settings, so I know it works), but
> that's a minor issue, as I can tinker with that later, and just use the
> keyboard to install for now.
> >
> > The real problem is that after
o I know it works), but
> that's a minor issue, as I can tinker with that later, and just use the
> keyboard to install for now.
>
> The real problem is that after going through the first three or four screens,
> the install halts, complaining about not being
Hi,
Kent West wrote:
> Warning: The driver descriptor says the physical block size is 2048 bytes,
> but Linux says it is 512 bytes.
The Apple Partition Map block size is 2048 indeed. Else it could not
coexist with the GPT.
> Disk /dev/sdc: 62.7GB
> Sector size (logical/physical): 2048B/512B
> Pa
t, here's what he writes:
1. The computer boots up the installation process ok.
2. It gets through the Ubuntu language, locale and keyboard selection.
3. Then starts loading additional components. At this point it gets
about a quarter of the way through then throws big error
Hi,
Kent West wrote:
> > I learned that EFI boot drives need to have a GPT partition table.
No. They do not. An MBR partition of type 0xEF is well ok, too.
> > discovered that the flash drive had a "mac" partition table.
> > Wha-a-ah-h-h??
It has an MBR partition table with partition 2 having
On Fri, May 11, 2018 at 2:59 PM, Pascal Hambourg
wrote:
> Le 11/05/2018 à 20:33, Kent West a écrit :
>
>>
>> I learned that EFI boot drives need to have a GPT partition table. On a
>>
>
> This is not correct. The UEFI specification supports boot from a drive
> with an MSDOS partition table. Other
Le 11/05/2018 à 20:33, Kent West a écrit :
I learned that EFI boot drives need to have a GPT partition table. On a
This is not correct. The UEFI specification supports boot from a drive
with an MSDOS partition table. Otherwise why would there be an "EFI
system partition" type identifier (0xe
seem to recognize the trackpad (which is
>> > recognized in the laptop's EFI firmware settings, so I know it works),
>> but
>> > that's a minor issue, as I can tinker with that later, and just use the
>> > keyboard to install for now.
>> >
>
On Fri, May 11, 2018 at 11:56 AM, Curt wrote:
> On 2018-05-11, Kent West wrote:
> >
> > The real problem is that after going through the first three or four
> > screens, the install halts, complaining about not being able to read the
> > CD-ROM.
>
> I wo
, as I can tinker with that later, and just use the
> > keyboard to install for now.
> >
> > The real problem is that after going through the first three or four
> > screens, the install halts, complaining about not being able to read the
> > CD-ROM.
> >
>
cognized in the laptop's EFI firmware settings, so I know it works), but
> that's a minor issue, as I can tinker with that later, and just use the
> keyboard to install for now.
>
> The real problem is that after going through the first three or four
> screens, the install h
On 2018-05-11, Kent West wrote:
>
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read the
> CD-ROM.
I would guess that in the installer's parlance it's referring to your usb stick.
Hi,
Kent West wrote:
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read the
> CD-ROM.
Report this to debian...@lists.debian.org and add the original messages
of the complaing software.
I'd s
st use the
> keyboard to install for now.
>
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read the
> CD-ROM.
>
> Googling the issue suggested a couple of possible fixes, but I've had n
er going through the first three or four
screens, the install halts, complaining about not being able to read the
CD-ROM.
Googling the issue suggested a couple of possible fixes, but I've had no
success yet.
Any help?
Thanks!
--
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com
. Loads on reboot.
> The problem I'm having is that CD-ROM module and device. Tried replacing
> "/cdrom (I'm sure that's not it, but whatever the default IS) with
> /dev/sda1 to no avail.
Sorry, but your post doesn't make much sense to me and the links
descri
the former verbatim, excepting, obviously,
> .iso filenames and kernel/RAM paths. CD 1 on 2GB /dev/sda1 partition; sda2
> for the system to be installed upon; sda3 for /home. Loads on reboot.
> The problem I'm having is that CD-ROM module and device. Tried replacing
> "/cdrom
talling I
followed the instructions from the former verbatim, excepting, obviously,
.iso filenames and kernel/RAM paths. CD 1 on 2GB /dev/sda1 partition; sda2
for the system to be installed upon; sda3 for /home. Loads on reboot.
The problem I'm having is that CD-ROM module and device. Tried replacin
On Thu, 10 Feb 2011 21:45:55 +, I wrote:
> [Lenny 5.0.2 install failed to detect the CD/DVD drive.]
On Fri, 11 Feb 2011 12:11:13 +, Camaleón responded:
> Your BIOS could to provide additional options for the storage controller.
> Have you tried, besides choosing AHCI, by explictly disabl
On Thu, 10 Feb 2011 21:45:55 +, Steve Kleene wrote:
> Today I got a new desktop and tried to install Lenny from a netinst CD,
> as I've done several times before. The install starts and sets the
> language but then fails at "Detect and mount CD-ROM" with these errors:
On Thu 10 Feb 2011 at 21:45:55 +, Steve Kleene wrote:
> I also tried booting from an 8-GB USB flash drive, which I made with:
>
> cat debian-502-i386-netinst.iso >/dev/sdc
I doubt this will work as it isn't a hybrid iso. You should be better
off with
http://www.debian.org/releases/stable/
Today I got a new desktop and tried to install Lenny from a netinst CD, as
I've done several times before. The install starts and sets the language but
then fails at "Detect and mount CD-ROM" with these errors:
"No common CD-ROM drive was detected.
...
Load CD-ROM dr
Tenenbaum wrote:
> Hi, again -- I recently posted on an issue with installing Debian Lenny on
> a new workstation with a Lite-On DVD writer. I had thought that the problem
> was the driver, but it turns out that my problem is a more familiar one, the
> "No common CD-ROM drive was det
iar one, the "No common CD-ROM drive was detected" error with SATA
> optical drives.
Strange... I did not see that error when installing Lenny from any of my
sata DVD drives :-?
Could this be related to the BIOS SATA mode? I expressly switch all my
computers to use AHCI (not "
Hi, again -- I recently posted on an issue with installing Debian Lenny on a
new workstation with a Lite-On DVD writer. I had thought that the problem
was the driver, but it turns out that my problem is a more familiar one, the
"No common CD-ROM drive was detected" error with SATA opti
On Fri, 2008-10-17 at 10:47 +0200, BALLABIO GERARDO wrote:
> Hi all,
> I'd like to ask for suggestions on how to check a cd-rom (or dvd-rom) against
> the original iso image to verify that it has been burned correctly.
>
> I tried a couple of methods, but I am not sure that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrei Popescu wrote:
> On Fri,17.Oct.08, 18:06:54, Dexter Filmore wrote:
>> snip
>>
>>> That doesn't quite work out:
>>>
>>> mount /cdrom
>>> /Fri Oct 17-06:14:44HDC5# md5sum /cdrom
>>> md5sum: /cdrom: Is a directory
>> Isn't /cdrom a symlink to /dev/
On Fri,17.Oct.08, 18:06:54, Dexter Filmore wrote:
> snip
>
> > That doesn't quite work out:
> >
> > mount /cdrom
> > /Fri Oct 17-06:14:44HDC5# md5sum /cdrom
> > md5sum: /cdrom: Is a directory
>
> Isn't /cdrom a symlink to /dev/cdrom...?
$ ls -l /cdrom
lrwxrwxrwx 1 root root 11 2008-07-11 00:40
thveillon.debian wrote:
> Hugo Vanwoerkom a écrit :
>> thveillon.debian wrote:
>>> BALLABIO GERARDO a écrit :
>>>> Hi all,
>>>> I'd like to ask for suggestions on how to check a cd-rom (or dvd-rom)
>>>> against the original iso image to
snip
> That doesn't quite work out:
>
> mount /cdrom
> /Fri Oct 17-06:14:44HDC5# md5sum /cdrom
> md5sum: /cdrom: Is a directory
Isn't /cdrom a symlink to /dev/cdrom...?
Maybe give it the real device path rahther.
Dex
--
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d--(+)@ s-:+ a C UL
1 - 100 of 860 matches
Mail list logo
